A Review of BONDtrv by Bruce S. Gray
BondTRV 2.0 - A Review
Spindex vs BondTRV
BondTRV 2.0 - A Review
WP Bond, from Professional Systems Development - A review by Michael Ruane - Phoenix Solutions.
Utility Diskette # 4
Reader's Clinic - AREV Runtime
QTIPS - Compiling Work around on runtimes
QTIPS - Runtime Version
Directory Exists on Novell
Utility Diskette # 4
Networked %SK%
Network Contention
Directory Exists on Novell
QTIPS - String Space Format Errors
QTIPS - Postscript Driver Problem
VERBatim - V17
VERBatim - V6
VERBatim - V125
Utility Diskette # 3 - Part I
Version 3 Technical Highlights - Copying Rows Programmatically
Version 3 TCL Subroutines - Copying Rows
Spindex - A Review
Spindex vs BondTRV
Utility Diskette # 4
Client Server Corner - SQL Server Data Loading Part I - Bill Wolff
Client Server Corner - SQL Server Data Loading Part II - Bill Wolff
SecureUser
VERBatim - V86
Advanced Revelation Initialisation Sequence (Overview) by Mike Pope
Reader's Forum - Mark Hirst Revelation C Interface - Part 1
Reader's Forum The C Interface Part 2 - Mark Hirst (Senior Techie - ICS) Reader's Clinic
VERBatim - V6
QTIPS - Suppressing Initial Form Feed
QTIPS - Using RTP29 In Place of V6
REVMEDIA Revisted
SecureUser
VERBatim - V25
@ATTACK - @Files.System
Advanced Revelation Initialisation Sequence (Overview) by Mike Pope
REVMEDIA Revisted
RTP Series - RTP57
RTP Series - RTP57A
LINEAR HASH FILE STRUCTURES - Part 1
RTP Series - RTP57
RTP Series - RTP57A
LINEAR HASH FILE STRUCTURES - Part 1
Vroom
Vroom - Window Processing
Reader's Forum
VROOM - Doubling MFS Write Speed
RTP Series - RTP42
RTP Series - RTP51
Reader's Clinic - AREV Runtime
@ATTACK - @PDisk.On
Advanced Revelation Initialisation Sequence (Overview) by Mike Pope
AREV Comes to Czechoslovakia Les Palenik, Cosmotron Systems
QUERY.SUB
QTIPS - Query Windows - Changing Colours
Readers Clinic - Quickly Coping with \
Utility Diskette # 3 - Part I
Utility Diskette # 3 - Part II
RTP Series - RTP9
RTP Series - RTP50
VERBatim - V25
@ATTACK - @Files
Utility Diskette # 3 - Part I
VERBatim - V86
@ATTACK - @Help.Level
@ATTACK - @Window.Level
Reader's Clinic - Screen Width
VERBatim - V41
VERBatim - V126
Esc.To.Exit
Uncommon Knowledge - WC_WST_CHAR%
@ATTACK - @List.Active
QTIPS - Btree.Extract
Comp
Reader's Clinic - Removing "Searching Cross References" Message
@ATTACK - @List.Active
IConvs / OConvs
Reader's Clinic - Stop Lists
REVMEDIA Revisited
REVMEDIA Revisited
V119 - Part I
V119 - Part II
VERBatim - V121
Utility Diskette # 3 - Part I
RTP Series - RTP42
VERBatim - V65
Argument passing - Subroutines and Functions - Mike Pope
Form.List.S
Make.Index
Index Sub Revisited
QTIPS - Make.Index 2.11+
QUERY.SUB
Version 3 Technical Highlights - Creating New Accounts Programmatically
Version 3 TCL Subroutines - Creating New Accounts
Version 3 TCL Subroutines - Creating Tables
Utility Diskette # 4
Readers Clinic - Quickly Coping with \
QTIPS - DOSTime
VERBatim - V11
@ATTACK - @Backgrnd.Time
@ATTACK - @Index.Time
QTIPS - Time-outs in Windows
RTP5 and RTP51
RevTi Just Wanna Have Fun
QTIPS - RLIST Average / Total Results

RevMedia FKB

DocumentV3I6A13
TitleBondTRV 2.0 - A Review
KeywordsBONDTRV
RLIST
BTRIEVE
TextIntroduction
Whilst it is not normally our policy to review software twice we thought
that WITH the growing interest in Client/Server technology it would be
beneficial to revisit BondTRV the BTRIEVE bond FROM Icicle Software The
latest version of the product not only includes a runtime version of Btrieve
for non Novell users but it provides Client/Server computing when used with
a full network copy of the Btrieve

Conclusion
Whilst not a "plug in and play" product like Spindex BondTRV is certainly a
lot easier to set up than SQL Server and can thus provide a much easier "in"
to the world of Client/Server computing The product is commercially mature
and benefits FROM a very robust user interface and API Once again Icicle
have shown how third party BFSs ought to be implemented The only failing is
the lack of extended Btrieve documentation provided WITH the package As a
newcomer to Btrieve I personally found all of the setup options daunting
and the coverage or Btrieve as a filing system was virtually non existent
however if you have Novell you will already have a Btrieve manual

What does BondTRV do?
BondTRV provides a complete replacement for the Linear Hash filing system
replacing it instead WITH the Btrieve filing system a filing system much
used in Novell applications and providing Client/Server capabilities The
Btrieve filing system being essentially fixed length WITH extensions for
variable length is more efficient at retrieving at speed than AREV
Consequently non indexed searches can be made much more quickly WITH Btrieve
than WITH AREV In addition to this BondTRV permits the establishing of
complex query filters which can then be used as "virtual fields" when query
commands are used for EXAMPLE a FILTER could be set up called
TRI_STATE_MONTHLY_REPORT which sorted by three criteria and only included
data FROM 3 states REPORTS could then LIST BY TRI_STATE_MONTHLY_REPORT and
BondTRV would provide optimised access to the Btrieve files

How does BondTRV do it?
BondTRV is implemented at the BFS level and as such integrates transparently
into the AREV environment Existing applications will run without
modification although changes will need to be made to allow access to the
enhanced features of the BondTRV bond In addition DIRECT programmatic
manipulation of the Btrieve data is made possible by a massively extended
equivalent to REDUCE and BTREE EXTRACT Rather than USING these two
routines BondTRV permits the user to define a sort order starting and
ending values and FILTER criteria within a special LABELLED common area and
then any subsequent READNEXT/READ loops are met USING the established filter
criteria When USING the server based version of Btrieve this can lead to
massive PERFORMANCE improvements Frank de Palo at XLTech REPORTS the server
based version taking less than 2 5 minutes to traverse a 200 000 record file
using this feature

In addition it is possible to make DIRECT CALLS to the BFS and this is well
documented in the user manual

How well does BondTRV do it?
The true test of a BFS is whether you can tell that it is there With
BondTRV you cannot unless you notice the improved retrieval times on
non indexed fields Because Btrieve uses explicit data typing BondTRV must
perform extensive domain validation Thus SETTING up BondTRV files for the
first time requires a knowledge of what is meant to be achieved as I am
not a Btrieve person it took several attempts to set up the test files
however the domain validation is superb and always tells you explicitly why
an operation has failed There are no "Null i/o error" messages rather
"Operation failed because the total length of the fields DEFINED (509 bytes)
exceeds the maximum DEFINED length of the record (500 bytes) "

Benchmarks
BondTRV does not position itself as a speed aid this is merely a side
effect of the efficiency of the BFS Further BondTRV can be used in both a
client server and a standalone MODE For this reason it is not considered
appropriate to provide comprehensive benchmarks of the product it should
be bought as an introduction to client server computing or as an interface
to existing Btrieve applications However tests by Frank de Palo at XLTech
comparing non indexed PERFORMANCE to standard AREV show a significant
improvement in throughput although some indexed queries were quicker under
AREV than WITH BondTRV

Supplier Details Icicle Software 907 Front Street Suite 204
Leavenworth WA 98826 (509) 548 5761 (Voice) (509) 548 7862 (Fax) Only one
licence needed whether single or multiuser $695


(Volume 3 Issue 6 Pages 11 12)
[revmedia/copyrigh.htm]

Page last modified: 31/01/03