S
Steve
We have a number of apps written in VB6 using DAO 3.5 to create and massage
the data. Quite often, we find a need to use ACCESS by itself to
manipulate one of the tables independently of the apps.
This wasn't a problem as long as we were using ACCESS 97 across the board.
Now that A2000 is finding its way on to many--actually most--of our systems,
we can't get away with it anymore.
Surely, we aren't the first outfit to run up against this. Nevertheless, we
have to deal with it and I'm not exactly sure how to approach it.
Ideally, I would like to be able to have the apps create and maintain tables
that would be compatible in both directions with either 97 or 2002 but my
gut feeling is that it ain't gonna happen.
Any advice as to how to approach this would be appreciated.
TIA..
the data. Quite often, we find a need to use ACCESS by itself to
manipulate one of the tables independently of the apps.
This wasn't a problem as long as we were using ACCESS 97 across the board.
Now that A2000 is finding its way on to many--actually most--of our systems,
we can't get away with it anymore.
Surely, we aren't the first outfit to run up against this. Nevertheless, we
have to deal with it and I'm not exactly sure how to approach it.
Ideally, I would like to be able to have the apps create and maintain tables
that would be compatible in both directions with either 97 or 2002 but my
gut feeling is that it ain't gonna happen.
Any advice as to how to approach this would be appreciated.
TIA..