Re: ADP (Write to local if loses connection to remote SQL Server?)

You might reconsider your data structures. I've never seen a case where the
mdb field-per-table limit was a problem. You didn't describe the data but
I'll guess. If you have the questions as individual fields, for example, you
could add a Question table that had columns for the form number, question
number, question text and question answer. Then you'd have many rows for
each form instead of many fields. Etc.

<kennethgrice@xxxxxxxxx> wrote in message
news:1179920804.897949.132740@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Hi,

I was thinking about using an ADP for a test form application.
Originially I was going to use Access, but I have too many fields.
It is about a 10 Form Test process. I was worried that in the middle
of the application, if the remote SQL Server becomes disconnected for
some reason, the tester would be stuck and couldn't go on. (My forms
are set to insert data from the form to a remote SQL Server by
clicking a Save button. Another command button then appears to
continue the test by launching the next for.

Is there some kind of code to put in the save button to send the data
to the SQL Server on the local machine if the default connection
cannot be reached? It would also be nice to notify an admin by email
if this happens to let them know that some of the data may be in the
remote table and the rest went to local. Or just making a label
appear on the form with this info if this is the case. Also, can the
data be saved in a local SQL Server in parallel to being sent to the
remote SQL Server. That would be a good backup.

Is any of this possible? If so, does anyone have an example? Thanks
in advance. I don't see the remote SQL Server going down much, but I
am just looking at failure modes right now.


.