Use ASP ODBC to Btrieve 6.1.5 receiving File is Lock Btrieve error 85 1

[eastman1]

I am working on a web project for my client. My client's accounting software is called Business Vision 32, v 6.15. Which used Pervasive Btrieve v.6.1.5 as the database. The database is stored in a server, the application connect to server and use Btrieve workstation engine which install on each individual machine.

My web project is to retrieve product infomration and post it on the web. To connect to Btrieve 6.1.5 database, I have obtained Pervasive workgroup engine v8 and correct DDF from the software vendor. Everything works fine, except when any user connect to the database and lockup the inventory file (INVENT.LCK), then the web page received File is lock, Btrieve error 85.

I have studied on the Pervasive web site and it seem I have to use same version of Btrieve engine to connect to database to preventing this from happening. Should I downgrade the web server to use ODBC v.6.1.5? (and how to obtain it?), or is they any way I can tap into the Btrieve v6.1.5 workstation engine, (I can install a copy of workstation engine on the web server, but I can not see ODBC for it)

Currently, there are no option for my client to upgrade to v8 engine. Any help is appreciated.

 

[mirtheil]

YOu are correct. The status 85 is because your are trying to use to different engines (not just versions, but engines) to access the data. To fix the status 85, you'll need to get both sides working using the same engine. The ideal solution would be to upgrade all of the machines to V8.6 (server engine if you've got more than 5 users). If that's not possible, you'll either need to copy the data to the web server and use the V8 engine there or use the 6.15 ODBC driver. The 6.15 ODBC driver was not included with the engine. It was a separate install and a separate product. Also, the ODBC 2.04 wasn't completely thread safe and wasn't completely 32 bit. You will have problems trying to use the Btrieve ODBC drivers. You might look at DataDirect. THey used to be Intersolv and have offered an ODBC driver for Btrieve 6.15 for a while.


Mirtheil
Certified Pervasive Developer
Certified Pervasive Technician
Custom VB and Btrieve development.

http://www.mirtheil.com

 

[eastman1]

Hi Mirtheil,

First I want to thank you to point me to a direction when I am totally lost on this Btrieve issue. You are really great as I also tried ODBC 2.04 and it gave me some general error. Which you explained it that is related to the "thread safe" issue. Thanks.

So I went to DataDirect and download ODBC 5.0, which contains a Btrieve compatible ODBC for Btrieve 6.1.5. I can use it to connect to Btrieve file. But one problem is it seems to hookup with my existing V8.6 workgroup engine I installed on the webserver, it does not hookup with the v6.1.5 workstation engine on the webserver that I intend it to use. If I shut down the V8.6 workgroup engine on the webserver, then the ODBC connection is lost. Message: "Record Manager Not Loaded - Error # 20" or Session no longer valid.

I have talked with my client, and they are not planning to go with V8.6 engine, as they are not comfortable to upgrade (i.e. cost; and worrying about one problem solved, new problem may pop). And copying data file to webserver also is not an option, as they wanted live data, and at some point, they want webserver to feedback to the Btrieve database, as matter of fact, I have done development on the webserver which has two way communication with the Btrieve database. (e.g. Display product info, take order, then push order back to Btrieve database). Everything works great until we discovered this file lock problem which stalls the development.

So my only option will be using Btrieve 6.1.5 workstation engine. I believe the workstation engine is installed when I install the Business Vision 32 application on the webserver, If I know how to utilize this workstation engine (display as "Gateway Server Btrieve 6.15" in the BV About screen), I guess the lock problem will be resolved. I guess the webserver will be considered as one of the application, which access the Btrieve files like other workstation.

Thanks!

Michael

 

[mirtheil]

As far as ODBC 2.04, the "General Error" is a common configuration problem not specifically the thread safe issue.
For the DataDirect driver, I would suggest uninstalling the 8.6 engine and reinstalling the 6.15 engine.
For the upgrade path, I would strongly suggest upgrading. 6.15 was last updated in early 1996 and hasn't been supported for a number of years. The current version is actually V9 (just released last week). You would want them to talk with BV to make sure they'll support it.
Getting all of the workstations using the same version (and same type of engine) is the key to the status 85 error.


Mirtheil
Certified Pervasive Developer
Certified Pervasive Technician
Custom VB and Btrieve development.

http://www.mirtheil.com

 

[eastman1]

I un-install v8.6 engine and DataDirect Btrieve ODBC picks up the workstation engine v6.1.5. This is amazing! Thank you so much!

I will conduct real live test in my client's office next week to make sure the status 85 will be gone with workstation engine v6.1.5, which the other stations are using. You have been very very helpful!

Thank you so much!

Michael