M
Mike Edwards
Further to my post on a problem on connectiong to SQL 2000 database's using
Access 2000 as a front-end (see below), as the Access 2003 version is
working correctly, should the Access 2003 Runtime version with the developer
extensions work in just the same way ?
Anyone using Access 2003 Runtime ?
Any problems or traps to watch out for ?
Regards
Mike
(I have transfered a medical database from Access 2000 to SQL 2000 (data
tables only), and re-linked the tables to a new Access d/base via ODBC -
everything seemed to be working OK, but then I found that only by using
Access 2003 would the pulldowns for patient records work correctly or store
modifications made to records.
The Access 2000 versions will not update records via pulldowns or save data
correctly.
I gave tried updating MDAC & Jet to the latest verions on the Access 2000
clients but have had no luck - the OS makes no difference either, I have
tried it on W2K & XP Pro platforms.
Does any one have any idea's on how to fix this problem with Access 2000 or
will I have to upgrade all clients to Access 2003 ?
Or could I use the Visual Studio Tools for Office and install the Access
2003 Runtime ?)
Access 2000 as a front-end (see below), as the Access 2003 version is
working correctly, should the Access 2003 Runtime version with the developer
extensions work in just the same way ?
Anyone using Access 2003 Runtime ?
Any problems or traps to watch out for ?
Regards
Mike
(I have transfered a medical database from Access 2000 to SQL 2000 (data
tables only), and re-linked the tables to a new Access d/base via ODBC -
everything seemed to be working OK, but then I found that only by using
Access 2003 would the pulldowns for patient records work correctly or store
modifications made to records.
The Access 2000 versions will not update records via pulldowns or save data
correctly.
I gave tried updating MDAC & Jet to the latest verions on the Access 2000
clients but have had no luck - the OS makes no difference either, I have
tried it on W2K & XP Pro platforms.
Does any one have any idea's on how to fix this problem with Access 2000 or
will I have to upgrade all clients to Access 2003 ?
Or could I use the Visual Studio Tools for Office and install the Access
2003 Runtime ?)