ODBC & Access on different computer

[becktho]

No, you don't have to register the database. In general you can copy the dsn to another system and access this dsn, but you have to ensure that the database path in the dsn is correct.

As you say it worked on the laptop and does not on the desktop, I still think it could be a pathproblem. Ok, it may sound stupid, but a path is one of the things that cause the most problems.

[DavidIMurray]

I have changed the path of the database but I have both edited the old dsn and also created a new dsn that points to the new path.

Cheers

Dave

[becktho]

Hm - what type of database ar you using? MS Access, MySQL, ...? I just used Access up to now and never had problems (although it is MS ;)).

[DavidIMurray]

Yup it is an access database. I'm going to try and recreate the exact paths for everything from one machine to the other. The problem is that when the system goes live it will be using a database on a remote machine so it need to be able to access other paths.

[becktho]

In general it should not be a problem to access the database on a remote system or network.

[DavidIMurray]

I'm still workign on this problem without success. Tried it on a third computer today and it still won't work. If used a list tables and columns to prove that it is connecting to the database. The problem is that it just won't extract any data - yet it works perfectly on the laptop it was created on.

Any help would be greatly appreciated.

Cheers

Dave

[rolfk]

---

@DavidIMurray wrote:

I'm still workign on this problem without success. Tried it on a third computer today and it still won't work. If used a list tables and columns to prove that it is connecting to the database. The problem is that it just won't extract any data - yet it works perfectly on the laptop it was created on.

---

Just a very wild guess but this can bite many people. Since it seems to work with the example on both computers but not with your code it might have to do with local settings. One common issue might be the decimal sign that you might for instance use for a conditional query. Another one might be the date format you use to define for instance a range of records to retrieve.

MS applications are notorious to take the local system settings into account anywhere and always and screw up such things for this reason. There are basically two approaches to fix this problem. The first one is to make sure the local settings are on all systems the same and the other one is to either use application specific methods to define local independant definitions or make your application to be compatible with multiple local settings.

Rolf Kalbermatter