by I have a database that writes to a SQL 7 table through
ODBC (Access 2000). The main server went down and we were
able to, relatively quickly, move to the backup server
(I'd been making backups all along and storing them off
the main database server, so it wasn't a problem to
retrieve them).
All was working well with the backup server, despite it
being slower than molasses in winter, and we finally got
the main server back up. In the meantime, the Acc 2000
application was used again. I didn't change the server
name to the main server (it had been on the backup
server's name), but all of a sudden I saw that data was
being written to the main server again. How could this be
without me changing anything on the client machine (I did
change my machine back to point to the main server, but
not the machine from which the client application runs)?
The client app had been writing to the backup server.
We are using TCP/IP connectivity, no cluster services,
with the SQL 7 Driver for ODBC, to connect between the
client and the server. I specified the machine name MAIL1
(the backup server) for the ODBC data source.
The problem with all of this is that the client seems to
be going back to the server before I get a chance to
restore from backup (so that the data that was written to
the backup server is now in the main server), and this
causes problems going forward.