Can I temporarily store data in an Access Project, before it reaches SQL Server?

Question

I am creating a Time and Attendance System using Microsoft Access 2003, Microsoft SQL Server Desktop Engine 2000.

Client machines are connected to the SQL Server over the net.

In case the net is down, i would like the client machines to store the information, then on a scheduled basis, send the information to the SQL Server.

Is this possible? If so, how do i do it?

Answer 1

You can, but not easily.

Access 2003 projects only support tables on the remote server. If your project cannot connect to the server, it will not open.

Solution A, which is messy: You could, theoretically, create a second, true Access database that links to the SQL tables in your project.

It would insert all data in a local table and then try to insert the same data into the linked tables. However, that's not a great solution.

Solution B, more elegant but more complicated: Create a new, true Access database that intentionally stores records locally, and has VB modules that attempt to connect to and store those records on your SQL server. When they cannot, the records are retained in the Access DB; when they cannot, the local insert is deleted.

Note to first two answerers: If you aren't going to be constructive, or you're just going to spout jibberish, please don't answer.

Answer 2

An Access Data Project has NO TABLES PHYSICALLY IN IT. The tables are LINKED from the SQL Server application.

Answer 3

what is Access used for? is this Web Based? if it is Web Based then you would not have to worry about storing data on the client machine. Storing data on the client machine can be really *touchy*. pose urself the question. If client A updates his spread sheet on pc1 then does it again on pc2 and trys to upload them both. what will happen? it could get messy, trust me i have done/seen this in action. A good solution is to have it Web Based interface to your SQL Server dbase and as long is the webserver is running (if hosted on a reputable site they are 99% online) then you dont have to worry about storing data on the client and the users can access on any machine that has internet connection...

hope this helped!
-o

Answer 4

i think of of you have fireplace walled your self out of the server. residing house domicile windows XP firewall or the a number of firewall you have 2 ideas, --- disable firewall (Use this to objective first) --- configure firewall to facilitates sq. server port open. sq. server facilitates connection over TCPIP / Named pipe. TCPIP connection is worry-unfastened to configure over firewall. one better factor the residing house version of sq. server facilitates purely one client connection at a time. So in case you're seeking to to connect better effective than one client which could be one in each of distinctive subject concerns. Get a conventional version of sq. server 2005 with new seen studio this may well be a 5 client reproduction.

Answer 5

OF course, its a computer.
The batch job that is scfripted to run and update the SQL server could run every 30 minutes for example

YOU sure dont know nothin about computers!!!