M
Mark
Hello again
I am migrating an MDB/MDE to MSDE/ADE (both XP).
Currently the front-end (mde) holds several tables which are used to
temporarilly store data for reporting etc. There are also tables in another
mdb (linked) on the local hard drive used for a similar purpose.
Using an ADP(E) then, what is the best way to store temporary data for
reporting etc.?
We are trying to avoid stressing the server too much (as it's low spec) and
keep network traffic down. There is a large amount of processing in some
cases and ideally I'd like to pull the raw data to the front-end or a local
mdb.
I gather its not possible to create tables which are stored in a front-end
ADE. Would it be better to use an MDE with linked tables then so some could
link to the server, others to an mdb, and if necessary some could be stored
in the mde itself (which is frequently refreshed or compacted btw)?
Many thanks
Mark
I am migrating an MDB/MDE to MSDE/ADE (both XP).
Currently the front-end (mde) holds several tables which are used to
temporarilly store data for reporting etc. There are also tables in another
mdb (linked) on the local hard drive used for a similar purpose.
Using an ADP(E) then, what is the best way to store temporary data for
reporting etc.?
We are trying to avoid stressing the server too much (as it's low spec) and
keep network traffic down. There is a large amount of processing in some
cases and ideally I'd like to pull the raw data to the front-end or a local
mdb.
I gather its not possible to create tables which are stored in a front-end
ADE. Would it be better to use an MDE with linked tables then so some could
link to the server, others to an mdb, and if necessary some could be stored
in the mde itself (which is frequently refreshed or compacted btw)?
Many thanks
Mark