"BTRCALL" or "XQLCompile()"

[EasyAim]

I'm used to using the API calls such as XQLCompile(), XQLFetch(), etc... in my VB6 applications.

However, I'm working for a new client who insists on using the BTRCALL() command for everything.

QUESTIONS:

* What is the underlying difference between the two sets of API commands? [i.e. between BTRCALL() and say XQLCompile()]

* Which is faster?

* Are there any other issues I should be aware of?

 

[mirtheil]

BTRCALL is the Btrieve interface, XQLCompile is the Scalable SQL interface.
Here's some pros and cons:
Btrieve API:
Transactional/Navigational (Open, GetFirst, GetNext, etc)Fast
Stable
Supported even with new versions of Pervasive (Pervasive.SQL 2000).

Scalable SQL:
Relational (Select * from table)
Unsupported after Pervasive.SQL 7.0 (P.SQL 2000 does not support it).
SLower than Btrieve (because Scalable SQL converts the XQL calls to BTRCALL calls evenutally).
Unsupported after Pervasive.SQL 7.0

Other issues may crop up. What programming language are you using? mirtheil@mirtheil.com
Custom VB and Btrieve development.
Certified Pervasive Developer
Certified Pervasive Technician

 

[EasyAim]

VB 6.0
The BTRCALL requires a lot more coding overhead but you're right - it is fast and stable.

 

[mirtheil]

Not only is it fast and stable but it's still supported by Pervasive. The Scalable SQL interface is no longer supported by Pervasive. mirtheil@mirtheil.com
Custom VB and Btrieve development.
Certified Pervasive Developer
Certified Pervasive Technician

 

[grnelson]

I had written a program to manage users and group Security in the Pervasive database using the Scalable SQL and found that it was instantly obsoleted by Pervasive 2000. So you should move away from the Scalable SQL. The Btrieve API does require a lot more work. I would recommend the ActiveX controls from Pervasive. They are fast and you can put a program togeather in a 20th of the time it would take writing using the Btrieve API.
Gil