Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations biv343 on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Unable to create new table

Status
Not open for further replies.

williey

Technical User
Jan 21, 2004
242
I'm trying to create a new table in a Access 97 DB. But the "New" button is greyed out. But both "Open" and "Design" buttons are available.

How can I unlock the "New" feature?

 
From the menu go to Tools, Security, User And Group Permissions.

IN the Dialog box there are two windows. Under the one on the right is a combo box labled object type. Drop that down to database (you will have to scroll up).

See if the admin user has administer permission. If not, someone has locked down the file so not just anyone can create objects in it. You should find the person who created the database and see about getting him to give you permission.

If however the author is long gone and you are a moral user of the system and should be able to access the entire database, then you can TRY to import all objects from the database into a new one. If you are LUCKY the admin user has read design permissions to all the objects and read data permissions for tables. By importing all the objects into a fresh file, you are the owner of the objects and get the default permissions for everything.

If you are UNLUCKY you don't have the necessary permissions and everything is locked down so tight that you can't import all the tables out or maybe some other objects. You MIGHT LOSE any database object in the new file. So if you go down this path, don't delete the original file.
 
Thank for the information. I have not used Access for almost 10 yrs now. The problem actually stems from opening a 97 Access DB in Access 2000 and 2003.

I managed to source a copy of the 97 Access and it worked.

What are the risks involved converting the DB to 2000 or 2003?

 
The biggest issue is DAO to ADO conversion. DAO code runs fastest in native 97 database running Acess 97 but ADO code runs faster than DAO... Or so I've read on these forums.

Other than that, Access creates a copy of the database in a different version so if something doesn't copy you still have the original to look at. The only catch would be if you had a problem in the converted version, did a bunch of data entry and for some reason had to go back to the earlier version. You could get around this by linking the older version tables in the newer version and then appending to them.
 
but ADO code runs faster than DAO
Not for Jet data.

Hope This Helps, PH.
Want to get great answers to your Tek-Tips questions? Have a look at FAQ219-2884 or FAQ181-2886
 
PHV,

Thanks for the correction.

I thought I smelled a rat in my recent dealings with ADO. Although it is new code so I had no baseline.

Is DAO faster than ADO in Access 200X?

Access 97 seems like to be a better product for standalone Jet applications.
 
DAO is faster than ADO for any Jet database.

Hope This Helps, PH.
Want to get great answers to your Tek-Tips questions? Have a look at FAQ219-2884 or FAQ181-2886
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top