December 1, 2003 at 10:29 am
We currently have roughly 50 Access Databases. We are trying to consolidate these into a SQL 2000 server. Currently (on some of our production equipment) if the MDB is down it will save the information locally. We need to make sure that if we switch to SQL that if the server goes down, the clients can still save the information locally and no data is lost. Is this a possibility or will I have to cluster this server with another?
Brandon
December 1, 2003 at 11:40 am
The saving data locally is something in the application, correct? It's not a SQL or Access thing AFAIK.
In SQL this will not occur automatically, the application would have to handle this.
Steve Jones
http://www.sqlservercentral.com/columnists/sjones
The Best of SQL Server Central.com 2002 - http://www.sqlservercentral.com/bestof/
December 1, 2003 at 12:06 pm
Since we are currently using Access 2000 for the front end (to the Access Databases) we have decided to contintue to use Access as the front end to SQL. You don't think this will be an issue? Is there a better way to solve this?
Brandon-
December 1, 2003 at 2:01 pm
There is no easy way to solve it. As Steve said, the app has to decide what to do if it can't connect to the server. If you've got a local data store (Access, MSDE), I'd go with that as a fallback. If you're using .Net, an option is to serialize to disk as XML, pick up later on and resubmit.
Andy
December 8, 2003 at 8:10 am
did you try to save information in local tables on Access ??
and make Yes/No (Bit) field on that local tables to let you know it this chages go to server or not ..
I hope this help u
Alamir Mohamed
Alamir Mohamed
Alamir_mohamed@yahoo.com
Viewing 5 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply