Consolidation of Databases Tables into one file!

  • Thread starter Thread starter JHB
  • Start date Start date
J

JHB

Hi:

I have a situation where I have a system with two files, the process
file "process.mdb" and the supposed database file "process_be.mdb".
Due to carelessness and lack of experience, I have ended up with some
of my tables in the file that contains the application code, namely
"process.mdb". Can someone either tell me how to move the tables that
are in the "process.mdb" file to "process_be.mdb", or tell me where I
can find the instructions.

Right now I have to keep the two files together, and I have to have
them both when I make any chances to tha application. I want to
disassociate the software from the database!

Thanks in advance

John Baker
 
Hi:

I have a situation where I have a system with two files, the process
file "process.mdb" and the supposed database file  "process_be.mdb".
Due to carelessness and lack of experience, I have ended up with some
of my tables in the file that contains the application code, namely
"process.mdb". Can someone either tell me how to move the tables that
are in the "process.mdb" file to "process_be.mdb", or tell me where I
can find the instructions.

Right now I have to keep the two files together, and I have to have
them both when I make any chances to tha application. I want to
disassociate the software from the database!

Thanks in advance

John Baker
Click to expand...

I should have mentioned I am working with Access 2000.

JHB
 
Hi:

I have a situation where I have a system with two files, the process
file "process.mdb" and the supposed database file "process_be.mdb".
Due to carelessness and lack of experience, I have ended up with some
of my tables in the file that contains the application code, namely
"process.mdb". Can someone either tell me how to move the tables that
are in the "process.mdb" file to "process_be.mdb", or tell me where I
can find the instructions.

Right now I have to keep the two files together, and I have to have
them both when I make any chances to tha application. I want to
disassociate the software from the database!

Thanks in advance

John Baker
Click to expand...

Have multiple users been updating these tables, each in their own copy of the
frontend? If so you've got a real mare's nest... if not:

Back up both databases (just in case something goes wrong).

Open process_be.mdb and use File... Get External Data... Import to import
these tables. It's probably a good idea to select Tools... Database
Utilities... Compact and Repair at this point (it's good routine maintenance
anyway, just so long as you have good backups!) Check to make sure you have
the expected data in thet tables.

Then open process.mdb. Open Tools... Options... General and be sure that Name
Autocorrect is *unchecked*. DELETE the tables that were misplaced. Compact
and repair the database; then use File... Get External Data... Link to connect
to the tables in the backend.

If you have multiple copies of process.mdb, each with its own *different* set
of data in these tables, post back with more details. This will be salvagable,
perhaps, but it'll be a lot more work!
 
Have multiple users been updating these tables, each in their own copy ofthe
frontend? If so you've got a real mare's nest... if not:

Back up both databases (just in case something goes wrong).

Open process_be.mdb and use File... Get External Data... Import to import
these tables. It's probably a good idea to select Tools... Database
Utilities... Compact and Repair at this point (it's good routine maintenance
anyway, just so long as you have good backups!) Check to make sure you have
the expected data in thet tables.

Then open process.mdb. Open Tools... Options... General and be sure that Name
Autocorrect is *unchecked*.   DELETE the tables that were misplaced. Compact
and repair the database; then use File... Get External Data... Link to connect
to the tables in the backend.

If you have multiple copies of process.mdb, each with its own *different*set
of data in these tables, post back with more details. This will be salvagable,
perhaps, but it'll be a lot more work!
Click to expand...

Thank you. Luckily I have not made the software available to the end
users yet, and did not want to until I got the issue sorted out!
 
Thank you. Luckily I have not made the software available to the end
users yet, and did not want to until I got the issue sorted out!
Click to expand...

GOOD thinking... <g>

So did the import/delete/relink sequence work to your satisfaction?
 
GOOD thinking... <g>

So did the import/delete/relink sequence work to your satisfaction?
Click to expand...

Sadly, there were some significant issues when I tried what you
suggested.

1. From the "process_be.mdb" file I went through the "get external
data process", only to find that the list of tables that showed up
included ALL tables, and not just those that were in the file
"process.mdb". Since I didn't want to duplicate the tables that were
already in the "be" file, I selected ONLY those that were supposedly
in the "process.mdb" file. (I identified these previously by opening
the "process.mdb" file and listing all tables that did NOT have a
check mark by them, on the assumption that those were the ones
embedded in the file. These I imported into the "process_be.mdb" file,
and did a "compact and repair".

2. I then attempted to open "process.mdb", and was unable to get it to
open!

As you suggested, I had backed up both files, so it wasn't hard to get
back where I started, but I have no idea what went wrong!

You got any clues what I did wrong?

Sorry..never done this before!

John Baker
2.
 
Sadly, there were some significant issues when I tried what you
suggested.

1. From the "process_be.mdb" file I went through the "get external
data process", only to find that the list of tables that showed up
included ALL tables, and not just those that were in the file
"process.mdb". Since I didn't want to duplicate the tables that were
already in the "be" file, I selected ONLY those that were supposedly
in the "process.mdb" file. (I identified these previously by opening
the "process.mdb" file and listing all tables that did NOT have a
check mark by them, on the assumption that those were the ones
embedded in the file. These I imported into the "process_be.mdb" file,
and did a "compact and repair".
Click to expand...

That was good thinking... and the correct procedure.
2. I then attempted to open "process.mdb", and was unable to get it to
open!
Click to expand...

It's probably trying to run some relinking code. Try opening it while holding
down the <Shift> key to bypass the startup.
 
That was good thinking... and the correct procedure.


It's probably trying to run some relinking code. Try opening it while holding
down the <Shift> key to bypass the startup.
Click to expand...

Thanks for your help. I think I have got it, however there was one
strange incident when I did the "Compact and Repair". The process
saved the compacted version with a new name, and set the old version
to read only, telling me to rename the new version to the old version.
When I did that, using the "compacted" version, it couldn't use it
because it appears that some of the field lengths had been changed. I
got an error that the data was too long for the field in the form I
was using! I then reverted to the non compacted version and it appears
to be working fine!

Thanks again.

If you have any insight into what could have happened in the
compacting process please let me know.

Regards
 
Thanks for your help. I think I have got it, however there was one
strange incident when I did the "Compact and Repair". The process
saved the compacted version with a new name, and set the old version
to read only, telling me to rename the new version to the old version.
When I did that, using the "compacted" version, it couldn't use it
because it appears that some of the field lengths had been changed. I
got an error that the data was too long for the field in the form I
was using! I then reverted to the non compacted version and it appears
to be working fine!
Click to expand...

There may be some corruption in the database. Try creating a new, empty
database and using File... Get External Data... Import to import everything
from this database. For more possibilities see Tony's corruption FAQ:
http://www.granite.ab.ca/access/corruptmdbs.htm
 
Back
Top