Why is Design View, Save, & Code View disabled after copying database (.mdb) file.

[egateway]

I'm attempting to copy an exisiting Access Database file (.mdb) to be used as beginning design for a new database; however Design View, Save, and other controls are disabled; why?

Platform: Windows XP
Errors: None

[Rabbit]

Did you copy from a CD? If you did it's probably set as read only in which case you'll have to set the read/write permissions of the file.

[MMcCarthy]

Or possibly they've been disabled in the startup options. Hold down the shift key when opening the database and you should see the full menu. Change the startup options.

Mary

[egateway]

Thanks everyone for the suggestions you've provided. However, after trying each suggestion I still have the same problem. One thing I noticed is that the unlike the forms the the tables do have the design view enbabled and when I select it I get the following message: "You can't modify the design of <table name> at a replica. Design changes to replicated objects can be made only at the Design master." The orginal .mdb file (database and forms) was copied from a working access application on our network to my workstation.

[MMcCarthy]

Thanks everyone for the suggestions you've provided. However, after trying each suggestion I still have the same problem. One thing I noticed is that the unlike the forms the the tables do have the design view enbabled and when I select it I get the following message: "You can't modify the design of <table name> at a replica. Design changes to replicated objects can be made only at the Design master." The orginal .mdb file (database and forms) was copied from a working access application on our network to my workstation.

By the sounds of it they didn't copy the database but created a replica. This is a kind of mirror of the database but I don't think you have many privilages with it. Ask them just to create a copy not a replica.

Mary

[NeoPa]

Sounds very like that to me too.
To make a copy of the file in the operating system (Windows Explorer in Windows) is what is required rather than creating a replica from within Access.

[egateway]

Sounds very like that to me too.
To make a copy of the file in the operating system (Windows Explorer in Windows) is what is required rather than creating a replica from within Access.

To create the copy of the .mdb file I simply 1) right clicked on the .mdb file 2) clicked copy and 3) pasted the file in the location I wanted; is this not the proper way to copy the file?

[MMcCarthy]

To create the copy of the .mdb file I simply 1) right clicked on the .mdb file 2) clicked copy and 3) pasted the file in the location I wanted; is this not the proper way to copy the file?

Yes it is but then the file you copied must be itself a replica.

[NeoPa]

Indeed.
Did you check that this behaviour was not duplicated on the original?

[egateway]

The original .mdb allows me to access the design view and make modifications to existing forms, tables, etc. however when I copy the file by doing a copy and paste of the .mdb file the design view is disabled and I'm not allowed to modify the forms, tables, etc.

[NeoPa]

In that case, just as a test, try to copy and paste this (original) file to your C: drive (assuming you have full rights there of course), and let us know the situation with the new copy.

[egateway]

Unfortunately, coping the .mdb file from the company's network share file area to my C drive on my workstation still presents the same issue of not being able to modify the copied version.

[NeoPa]

Well, I have to admit to being stumped.
There's nothing I know of that would cause a file to behave differently after a simple file-copy is made (except file permissions of the resultant file but that isn't the case here it seems).
If I get any inspiration I'll share it, but for now I'm stuck :(

[Rabbit]

Try making a copy into the same place as the original and see what happens.

[egateway]

Coping the file to the same location/folder produced the same issue. I know it would take some time but could I create a new access database and simply copy the code from the original database to recreate the forms and export the data from the original tables into the new tables? Basically recreating the entire application from the code and data?

[Rabbit]

It actually wouldn't take much time at all.

Create a blank database and you can import everything from the original: Modules, Forms, Reports, Tables, Macros, Queries, everything can be imported.

[MMcCarthy]

Unfortunately, coping the .mdb file from the company's network share file area to my C drive on my workstation still presents the same issue of not being able to modify the copied version.

Just out of curiousity, right click on the mdb file that you've copied and see if the file is Read Only.

Mary