ODBC from Btreive. Access 97 2

[Harri1976]

I am having some issues with extracting data from a btreive Database.

Using Access 97 to Extract data from a Btreive database. This worked fine before all the passwords on the domain changed, the Btreive ddf files are on a member server and the ODBC is on another server, using mapped drive to extract the info, running the make table query and get the error "Login Must succedd before data source entry can be written" Status code 2103. The database has no security on it which would require a login, has tried mapping a drive as the administrator, but still get the same errors.

Does anyone have any ideas.

 

[TomKane]

What version of btrieve are you using? Are you using a DSN on the client PC to connect to the data?

 

[Harri1976]

Hi

We are using Btrieve v 7.0 and a System DSN on the Client PC.

 

[TomKane]

It sounds like it's a rights/permissions issue with Pervasive on the server more so than on the client PC - if your're using an NT/2000 environment you might go to your databe and give it "every one/full control" and see can you create the table then.

 

[Harri1976]

I have changed the permissions on the DB directory, to everyone Full Control, but still seem to be getting the login error message. The log file doesnt give any errors, on the client or server, it only indicates that resources are being allocated or realased.

 

[mirtheil]

A status 2103 indicates that the SQL engine couldn't be loaded. Can you use SQLScope from these machines? If not, are you also getting a 2103?
Also, what are the "Target Engine" settings set to on the server where ODBC is being run?

info@mirtheil.com
Custom VB and Btrieve development.
Certified Pervasive Developer
Certified Pervasive Technician

 

[Harri1976]

Using SQLScope on one client give the error message 2103, but running it on the server where there database is, gives the a 802 error, the Target Engine is set to (1) Have checked the services on the server and Sql Scable service i running

 

[Harri1976]

I am still getting the error using the SQlscope on the client, managed to VPN on to the Server and can use the Sqlscope and create new ODBC connections without any errors, however still getting the 2103 error using the client. We have about 20 connecrtins to these databases and none of them work. Any more ideas.....

 

[mirtheil]

The TargetEngine on the Clients (assuming they are WinNT/Win2k/WinXP) machines needs to be set to 0.

info@mirtheil.com
Custom VB and Btrieve development.
Certified Pervasive Developer
Certified Pervasive Technician

 

[Harri1976]

Hi

I have managed to resove the issue, the server had had its network cards replaced the new ones were bound together using different IP addresses, unfortunlaty i am based in Vancouver BC and the server is in Newcastle, England, so a bit difficult to get things changed.

Many thanks for you help