adams.bria
Registered User.
- Local time
- Today, 12:08
- Joined
- Apr 28, 2010
- Messages
- 41
3 different programs run on the same set of biographical data. These programs perform surveys and track participants progress. Ideally I wanted to create three separate front ends so that each program could be customized to fit the specific needs. However, the front ends want to be able to come 'off the network' and go to remote places with no internet access. So here is my thought, and I am curious if someone could enlighten me to my mistakes, warn me of potential problem, or let me know if this will work in general.
Have one database with strictly bio data that is shared across all three programs. This is entered with one front. On the db's for the 3 programs, have a macro that checks for changes to the bio data from the bio data db each time it is started. Thus if it would be started when it is not on the network, it would just have the old bio data still in the tables, meaning it could be used off the network (locally) as well. I know it isn't ideal, but I think it could work. It would mean a lot more backing up of the db that is on the laptop as soon as they get back to the office, but it should accomplish my goal.
Thanks for the input in advance,
Brian
Have one database with strictly bio data that is shared across all three programs. This is entered with one front. On the db's for the 3 programs, have a macro that checks for changes to the bio data from the bio data db each time it is started. Thus if it would be started when it is not on the network, it would just have the old bio data still in the tables, meaning it could be used off the network (locally) as well. I know it isn't ideal, but I think it could work. It would mean a lot more backing up of the db that is on the laptop as soon as they get back to the office, but it should accomplish my goal.
Thanks for the input in advance,
Brian
