Access 2000 and XP
-
I am currently developing two seperate projects, one using Access 2000 and one using Access XP (On two different machines, both with IIS). With Access 2000, I must close the database before my asp page can access (database in use error), whereas with XP I don't. Is it possible to replicate the XP behaviour in 2000, or is the problem not related to access? - Xavier
-
I am currently developing two seperate projects, one using Access 2000 and one using Access XP (On two different machines, both with IIS). With Access 2000, I must close the database before my asp page can access (database in use error), whereas with XP I don't. Is it possible to replicate the XP behaviour in 2000, or is the problem not related to access? - Xavier
Hi Xavier, I have'nt worked with AccessXP (for the fact, Office XP suite of products). But with Access 97 or Access 2000, the catch is when MDB is open via MSACCESS Interface PRogram, nobody else could open that and you will get an error 'The database already open and is exclusively locked by user in machine12' It is not a problem though. But it is a limitation of Microsoft Access. If you need more scalability and connections, you can try MSDE (Microsoft Desktop Engine) -- the scaled down version of Microsoft SQL Server 2000. Deepak Kumar Vasudevan
-
Hi Xavier, I have'nt worked with AccessXP (for the fact, Office XP suite of products). But with Access 97 or Access 2000, the catch is when MDB is open via MSACCESS Interface PRogram, nobody else could open that and you will get an error 'The database already open and is exclusively locked by user in machine12' It is not a problem though. But it is a limitation of Microsoft Access. If you need more scalability and connections, you can try MSDE (Microsoft Desktop Engine) -- the scaled down version of Microsoft SQL Server 2000. Deepak Kumar Vasudevan
Thanks for that I'm afraid upgrading from Access 2000 isn't an option at this stage, although it's good to know that it not possible, might give me some leverage... :) - Xavier