Backup Data = Recordset Not Updatable

[Tracey_Gigatta]

I have a couple front-end databases that all link to another database of only
data tables. I have a batch file that runs nightly to back-up these
databases via Scheduled Task. I have been doing this for years. Now, all of
a sudden, on occassion after the back-up occurs, the data tables database
appears to be locking data. When trying to enter new data or records from
forms on the front-end databases, I get an error on all of them that "this
recordset is not updatable". I'm pretty sure it's not the front-end
databases, because the only way I have found to fix this is to go back to the
day's prior data tables and re-link to them. Then it works -- except now, I
have lost data. Can someone help me please? Thanks in advance. Hope this
makes sense.

 

[Tracey_Gigatta]

One more thing, the batch file is "copying" the database, not sure if that is
different that "backup".

 

[Tracey_Gigatta]

I found something ... after the copy occurs, the relationships are not
updating. They are all gone. Why would this "sometimes" happen?

 

[aaron.kempf]

uh if you want to BACKUP your database; then you need to move to SQL
Server.

Sorry- Access doesnt' support reliable backups.

-Aaron

 

[aaron_kempf]

If your DB isn't reliable enough to get backed up then you should move
to SQL Server

 

[Roger Carlson]

Actually, the simplist way to back up a database is with the Compact method.
You can do it with a single line of code:

DBEngine.CompactDatabase "C:\original\path\and\filename.mdb",
"C:\original\path\and\newfilename.mdb"

You can even use the Scheduler to run this by creating a brand new database.
Create a new function (it must be a function) with the above line of code.
Create a Macro that has a single action (RunCode) which runs the above
function. Then simply run the database from the command line in the
scheduler with the /xMacro switch (replacing "macro" with the actual name of
your macro).

I've got a couple of samples on my website (www.rogersaccesslibrary.com)
that might help: "CompactBackEndDB.mdb" and "RunRemoteMacro.mdb".

--
--Roger Carlson
MS Access MVP
Access Database Samples: www.rogersaccesslibrary.com
Want answers to your Access questions in your Email?
Free subscription:
http://peach.ease.lsoft.com/scripts/wa.exe?SUBED1=ACCESS-L

 

[Tom Wickerath]

Hi Tracey,

You might try rebuilding your BE database, just to help rule out any
possible corruption problems. Use the instructions that I provide on the
bottom half of page 3 of a Word document that I call "Access Links". You can
download a zipped copy from this location:
http://www.accessmvp.com/TWickerath/

After rebuilding your BE database, you might also want to rebuild the linked
tables in your FE database. Delete all linked tables in the FE, compact the
FE, and then re-establish the links from scratch using File | Get External
Data | Linked Tables. Of course, you'll need to distribute this FE to others,
if this is a multi-user Access application. (Hopefully, you have each user
running their own copy of the FE application, and not sharing a common copy,
right)?

Implementing a Successful Multiuser Access/JET Application
http://www.accessmvp.com/TWickerath/articles/multiuser.htm


Good Luck,

Tom Wickerath
Microsoft Access MVP
http://www.accessmvp.com/TWickerath/
http://www.access.qbuilt.com/html/expert_contributors.html
__________________________________________

 

[Tracey_Gigatta]

Thank you both Roger & Tom.

Actually, the simplist way to back up a database is with the Compact method.
You can do it with a single line of code:

DBEngine.CompactDatabase "C:\original\path\and\filename.mdb",
"C:\original\path\and\newfilename.mdb"

You can even use the Scheduler to run this by creating a brand new database.
Create a new function (it must be a function) with the above line of code.
Create a Macro that has a single action (RunCode) which runs the above
function. Then simply run the database from the command line in the
scheduler with the /xMacro switch (replacing "macro" with the actual name of
your macro).

I've got a couple of samples on my website (www.rogersaccesslibrary.com)
that might help: "CompactBackEndDB.mdb" and "RunRemoteMacro.mdb".

--
--Roger Carlson
MS Access MVP
Access Database Samples: www.rogersaccesslibrary.com
Want answers to your Access questions in your Email?
Free subscription:
http://peach.ease.lsoft.com/scripts/wa.exe?SUBED1=ACCESS-L

 

[lack32]

To fix this error review any table design changes you might have mad
change key fields, remove key fields, replaced table with one fro
another db. If it is then change it in original form. You can instal
new latest Microsoft Data Access Components which fix many error
because sometime it cause due to version issues. You can try compac
the database, and if that doesn’t help try recreating the query: ope
it in SQL view; copy and paste the SQL text to Notepad; delete th
query; create a new query and paste the SQL back or you can go for thi
method. First open the database and check the user and group permission
via tools on the menu. Make sure that the objects (Tables) you want t
update have the update permission checked. Secondly Ensure the tabl
owner is you or admin and not the person who developed. For mor
information click here :http://tinyurl.com/4ve53v

 

[xiaojun]

To fix this error review any table design changes you might have made
change key fields, remove key fields, replaced table with one from
another db. If it is then change it in original form. You can install
new latest Microsoft Data Access Components which fix many errors
because sometime it cause due to version issues. You can try compact
the database, and if that doesn’t help try recreating the query: open
it in SQL view; copy and paste the SQL text to Notepad; delete the
query; create a new query and paste the SQL back or you can go for this
method. First open the database and check the user and group permissions
via tools on the menu. Make sure that the objects (Tables) you want to
update have the update permission checked. Secondly Ensure the table
owner is you or admin and not the person who developed. For more
information click here :http://tinyurl.com/4ve53v