jottiwell
Feb 14th, 2000, 11:38 AM
I'm having a number of problems with systems at the moment, if you can help with those, please see my other posts, any help would be appreciated.....
Does anyone know of any incompatability problems between Access 2000 and 97?. I run a database which uses an Access 97 database as a data store, and a Access 2000 database purely as a front end, which is linked to the 97 back end store.
The only reason I'm not running a 2000 back end store is that I can't find a version of JetComp which will open 2000 spec databases in order to repair them, therefore if a 2000 store went down and Access 2000 couldn't open it I'd be stuffed. If anyone knows of a version of JetComp, or perhaps understands whether the revisions to the inbuilt Access 2000 repair / compact utility can handle corrupt databases ( i.e. those which won't even load ( invalid format etc. )), could they please let me know.
I've just had a situation where the Access 97 back end store corrupted. I kicked everyone out of the system, Jetcomped the 97 store, any everyone went back in happy as larry. Then when I opened a linked table in the 2000 front end and tried to add a record, as soon as I pressed a key, about 70% of the fields in the table displayed #error# and reported a unreserved error. If I open the table in 97 however, and add a record, it works!!. Does anyone know of any incompatibilties that would cause this?, interestingly re-linking the tables into the 2000 version seemed to cure it, but it makes me worry that things like this behind the seens and go unchecked, because the jetcomp utility would report that the 97 back end is fine.
Please help if you can, it may be an important piece of a particulary nasty puzzle I'm trying to solve at the moment,
Thanks in advance...
Does anyone know of any incompatability problems between Access 2000 and 97?. I run a database which uses an Access 97 database as a data store, and a Access 2000 database purely as a front end, which is linked to the 97 back end store.
The only reason I'm not running a 2000 back end store is that I can't find a version of JetComp which will open 2000 spec databases in order to repair them, therefore if a 2000 store went down and Access 2000 couldn't open it I'd be stuffed. If anyone knows of a version of JetComp, or perhaps understands whether the revisions to the inbuilt Access 2000 repair / compact utility can handle corrupt databases ( i.e. those which won't even load ( invalid format etc. )), could they please let me know.
I've just had a situation where the Access 97 back end store corrupted. I kicked everyone out of the system, Jetcomped the 97 store, any everyone went back in happy as larry. Then when I opened a linked table in the 2000 front end and tried to add a record, as soon as I pressed a key, about 70% of the fields in the table displayed #error# and reported a unreserved error. If I open the table in 97 however, and add a record, it works!!. Does anyone know of any incompatibilties that would cause this?, interestingly re-linking the tables into the 2000 version seemed to cure it, but it makes me worry that things like this behind the seens and go unchecked, because the jetcomp utility would report that the 97 back end is fine.
Please help if you can, it may be an important piece of a particulary nasty puzzle I'm trying to solve at the moment,
Thanks in advance...