Topic awaiting preservation: slight detour URGENT (Page 1 of 1)

okies anyone upto speed with access error messages? in hope of a quick fix! (clients kill a database and then back up the file and overwrite the good one)

ok got a call from a client i did an access database for that feeds a website..

they did an update a week ago went to do an update today..

they add record either at form level or table view and try to save and it throws up all kinds of errors unabkle to save file, EOF MET,invalid argument amongst a few..

so i went o have a look and yup the tables trashed in edit mode..can still be read etc but not updated everything is fooked all the ole obects goofed too

so i checked all the settings they were fine but cant add new record or edit it...checked all file permissions etc...

ok so step 2....restore from back up...

nope...

newbie in their office changed back up settings to daily and not incremental and overwrite original files... so for the last god knows how long they have been backing up the f...d up database....

now i have an older version of the database some 3 months out of synch...lots of work rentering data and then deleting non valid records etc..

is there anyway of opening a table and copy and paste to another db at the same time....tried export/import but that didnt work either...

i think its down to them and a lesson they wont forget...but would prefer to give them something a bit more constructive...
thanks

You might want to try an ASP/access forum. I only think there are a couple wondering these halls. Most of us shy away from proprietary solutions and turn towards open source ones. PHP/MySQL by far being the favorite in here.

WM Thx,

again this was a classic case of the client saying i want it this way take it or leave it; guess they learned the lesson

I?ve come across this sort of thing before, and while it isn't pretty you can do a copy and paste style thing between two databases with pretty much any language that supports odbc.
here's a quick bit of vb-esque pseudocode as an overview of what you need to be doing:


define and create and open two connection objects one for each database
define and create one recordset

set recordset = connection1.execute(select * from table1a) ' where table1a is the table in the knackered database)

do while not recordset.eof
do a bit of data integrity checking here if necessary
connection2.execute(insert into table1b values(col1, col2, col3, ..., colx)) ' table1b is in the shiny new uncorrupted database
loop

although as I say it isn't pretty, something like that should do you just fine and allow you to populate the new database with all the older databases information, making your client eternally grateful

good luck
I:.

Cheer! will give it a try later

well just to let you know what happened.

Got a call from the client apologising for screwing up my hard work for them, they have taken on a temp and she and the person who messed it up are repopulating an old test back up i found which isnt that far out of date. I suggested the other options and they decided to go it their way. So all in all they are happy with my end..not so happy with the dummy that goofed it up. they are now using a different backup method . and i just landed some more work from them.

so thx everyone

top news - you don't have to do the graft and you still get more work from them
congrats
I:.