Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Pervasive SQL Config problem?

Status
Not open for further replies.

trims30

Programmer
Dec 17, 2000
22
US
We are the developers of TRIMS, a program distributed with Btrieve 6.15 workstation engine. One of our customers is using it with Pervasive SQL 8 WorkGroup Edition and is experiencing problems with one workstation.

Please read problem description below.
Anyone have an idea as to what's happening?

Lee

==================
Data files reside on an NT4 server.

All of the client workstations have a mapped drive pointing to the Trims2k share on that server.

All of the 4 clients at the maintenance shop point to that server for the Trims data.

None of the clients including Linda have any data on their PCs.

Everyone can work normally whether or not Linda’s PC is turned On or Off.

If Linda starts Trims first then she and everyone can work normally but if anyone else starts Trims first then everyone but Linda can work.

If Linda’s PC is powered off for a week everyone can work fine because Linda’s PC is not where the data is...data is on the NT 4 server.

If everyone has their PCs on and not in Trims then Linda can start Trims without any problem or if everyone else gets out of Trims then Linda can start Trims without any problem.

==================================

 
Sounds like you've got multiple engines accessing the data. Is Linda's PC the only one with the V8 Workgroup engine? If so, that's the problem. Everyone else is using 6.15 and the two engines can't access the same data at the same time.

Mirtheil
Certified Pervasive Developer
Certified Pervasive Technician
Custom VB and Btrieve development.
 
mirthiel:
I've been told that all workstations are using PSQL.

That's the first thing I thought of. We distribute the 6.15 library but customer has installed PSQL.

It is possible that customer reinstalled our software and overwrote some of the PSQL routines of same name as Btrieve 6.15 components in Windows\System32 folder.

I'll have them reinstall psql on Lindas machine.

Lee
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top