When db copys it gets corrupted

[jmj]

Hi,
I've never seen this before. We were copying a db to its new server. This is usually a simple copy/paste. Not only did copy/paste not work, I also made a brand new db and imported all of the objects into it.

However, both ways seem to corrupt, this is what happens:
1. When adding new data, some information will not insert into a particular table.
2. When I go back to look at the ORIGINAL database the data (from #1) is inserted twice into that copy of the table.

It's almost like the location of one table is hardcoded into some of the vb code or something, although I don't see anything like that right off hand.

Has anyone else had something similar/know where I should look.
Thanks,
J

 

[Golom]

Look at your linked tables. They are hard-coded with respect to the path to the database that actually contains the table. Copying a database to a different location will not change the link paths but, if it's not on the same machine, those paths may no longer point to the correct place (or to any place at all.)

 

[jmj]

That is the strange part. There are NO linked tables in this database, all local tables. I've copied lots of dbs with local tables and never saw this issue before, usually you can make a new copy anywhere.
That's why I can't figure out why it's linking back to the old table. There are some buttons to push that refresh the data/insert the data into this table. It must be hardcoded in that vb code somewhere/somehow.
j

 

[JoeAtWork]

Try using the path to the original database as a search parameter. That should lead you to the code that's doing the update.