G
Guest
We have a small number of people who would like to use a Timesheet
application out of the office. I'd rather not climb the Replication learning
curve, but wanted to get opinions from experts here about the strategy I'm
considering.
The main data input form and its subform are each based on a single table.
I plan to put a renamed subset of these two tables in a separate back-end
file, stored on the user's hard drive, and linked into the front-end.
When the user loads the database, the form will be loaded based on the dummy
tables. On exit, a connection to the server will be checked--if it exists,
update queries will be run to transfer the records to the genuine tables, so
that management has the most up-to-date data available. If not, it will
simply exit.
It seems that it should work to me, but I wonder if I'm missing something.
Does anyone have an opinion?
application out of the office. I'd rather not climb the Replication learning
curve, but wanted to get opinions from experts here about the strategy I'm
considering.
The main data input form and its subform are each based on a single table.
I plan to put a renamed subset of these two tables in a separate back-end
file, stored on the user's hard drive, and linked into the front-end.
When the user loads the database, the form will be loaded based on the dummy
tables. On exit, a connection to the server will be checked--if it exists,
update queries will be run to transfer the records to the genuine tables, so
that management has the most up-to-date data available. If not, it will
simply exit.
It seems that it should work to me, but I wonder if I'm missing something.
Does anyone have an opinion?