Killing the off-line database

[Janis Rough]

Having to kill the off line database to add new records seems a little
extreme if you have to do it every day but thank you for the answer. I
think they will should have a wireless connection anyway. I am sorry I
really don't know how Windows wireless works. In any case what about Active
Server pages? Is it secure for only a company intranet. Is there a way to
only allow connections to the database via Active Server pages only from
desinated IP's? Also, say the .mdb database is on a wireless network can
those people still navigate through the network to get to the .mdb database.
In that case they would still be online I guess. I'm sorry I don't
understand windows networking.

Thanks,

 

[Guest]

Hi Janice.

You don't need to kill the DB. I gavew this only as an example. You can
take bits of the code and use it. I use this code (kill) as I look after a
large amount of off-line stand alone DB that need up[grtadeing with new costs
etc on regular basis. BUT you are doing it in the opposit direction.

I would suggest you may want to look at simply using the excel workbook and
then - when you want to import - just do this into a table written for this
and then run an update to apend the records to the main table(s). You should
be able to do this on an autoexec once you have set it up.

Good luck