D
Debbie S.
I created a database and stored it in a folder on my c drive. I then used the
database utility function in access to split the database, and then I created
a backup. At some point I moved all three of these files--the original (we'll
call it database y.mdb), the backup (database y_datebackupfilecreated.mdb),
and the back end (databasey_be.mdb)--into a new folder, still on my c drive.
Now for some reason when I open the file called database y.mdb, I get a
message that says the path is not valid. The path quoted in the message is
the OLD folder name; and, if I click okay on the message, I can see in the
database window that the tables in database y.mdb are the split ones that
have the arrows by them. Why won't the file open, and why does the original
file I created store the split tables? I thought the whole point of splitting
was to create a file that is based on the original that will not allow users
to mess with the tables. Why does the original file have the split tables?
I'm confused. Can someone please help me clear this up.
Many Thanks,
Debbie
database utility function in access to split the database, and then I created
a backup. At some point I moved all three of these files--the original (we'll
call it database y.mdb), the backup (database y_datebackupfilecreated.mdb),
and the back end (databasey_be.mdb)--into a new folder, still on my c drive.
Now for some reason when I open the file called database y.mdb, I get a
message that says the path is not valid. The path quoted in the message is
the OLD folder name; and, if I click okay on the message, I can see in the
database window that the tables in database y.mdb are the split ones that
have the arrows by them. Why won't the file open, and why does the original
file I created store the split tables? I thought the whole point of splitting
was to create a file that is based on the original that will not allow users
to mess with the tables. Why does the original file have the split tables?
I'm confused. Can someone please help me clear this up.
Many Thanks,
Debbie