Keep data in front and back end.

[Ron]

I'm looking at setting up a database with a front-end and
back-end. The front-end will reside on a laptop with a
wireless connection, and the back-end will be on a
network drive.

What I'd like to do is when data is entered on the
laptop, have it put the data in the network back end, but
ALSO have it insert it into the front end.

What I'm concerned about is that the person using the
laptop might wander into in an area of the plant where
the wireless connection might not work. If the db can't
get to the b-e it will freak out, so I want to be able to
store it in the f-e... even if only temporarily so that
the laptop user can continue to enter their data without
interuption (and hopefully without even realizing he/she
has lost connection to the B-E).

Then the ideal situation would be for the F-E's version
of the data to automatically update to the B-E. Once
again, the ideal situation would be that the data in the
back end is never more than a couple minutes old.

Suggestions or ideas?

 

[Tim Ferguson]

What I'm concerned about is that the person using the
laptop might wander into in an area of the plant where
the wireless connection might not work.

Sounds like database replication..?


Tim F

 

[TC]

There is no way, AFAIK, that the FE will be able to handle unexpected
disconnections gracefully. The FE will fail, & the BE will probably be left
corrupted. Access/Jet does not provide failover capabilities of this kind,
at all.

HTH,
TC