|
|
|
|
![]() ![]() |
Apr 7 2008, 03:17 PM
Post
#11
|
|
|
Member - Active Contributor Group: [HOSTED] Posts: 97 Joined: 3-April 08 From: Milling about Member No.: 29,596 |
Hello, to assist in resolving this issue I have a few questions that need to be answered.
The database in question: Are you working with it directly? Is the .mdb file on your local machine? Is the database set up as a single user application or as a client/server app? If the Database has a front end are you able to create or edit data through it? Did your client provide you with a user name and password to work on the database? Have you attempted to open the database file exclusively? Does the client have a backup of the workgroup file? Have you tried to delete and replace it? Lastly, for now, what is your exact error message? Answering these questions may well lead you to a resolution if not post the answers. |
|
|
|
Apr 8 2008, 11:02 AM
Post
#12
|
|
|
Super Member Group: [HOSTED] Posts: 713 Joined: 8-April 06 From: Lima - Peru Member No.: 12,579 |
Hello, to assist in resolving this issue I have a few questions that need to be answered. The database in question: Are you working with it directly? Is the .mdb file on your local machine? Is the database set up as a single user application or as a client/server app? If the Database has a front end are you able to create or edit data through it? Did your client provide you with a user name and password to work on the database? Have you attempted to open the database file exclusively? Does the client have a backup of the workgroup file? Have you tried to delete and replace it? Lastly, for now, what is your exact error message? Answering these questions may well lead you to a resolution if not post the answers. Ok, here are my answers:
Best regards, |
|
|
|
Apr 8 2008, 03:09 PM
Post
#13
|
|
|
Member - Active Contributor Group: [HOSTED] Posts: 97 Joined: 3-April 08 From: Milling about Member No.: 29,596 |
Ok, here are my answers:
Best regards, From the information I have there are a couple of possibilities. Since the description sounds as if you are able to actually open the database in Access and see the objects but not view the objectys you may well have a corrupt DB. The Access repair tool may well resolve your issue. Or In Access you can set permissions for the database allowing various user levels with various levels of access to add or manipulate the data or design. When this is done a separate file with an MDW extension is created. This file is the Workgroup file. It seems that you have the MDB file available to you but not the MDW file. What you will need is either to get hte MDW file and a Username and Password for it. You can read all about Access security from Microsoft. |
|
|
|
Apr 8 2008, 09:54 PM
Post
#14
|
|
|
Super Member Group: [HOSTED] Posts: 713 Joined: 8-April 06 From: Lima - Peru Member No.: 12,579 |
Tell me, the Access repair tool is the one located under the Database Utilities submenu under the Tools menu or it is a stand alone application??? if it is the second option from where i can download it because i just search it without success.
When i first copy this database i dont copy the MDW file that you say, so, if i get this file from my client every thing will work??? Also, i notice that this file can be located in a folder that i choose but, where is the default location for it?? BTW, Can i use Visual Basic to access this database??? and thanks for the access security link i'm start reading it, very useful. Best regards, |
|
|
|
Apr 14 2008, 02:14 PM
Post
#15
|
|
|
Member - Active Contributor Group: [HOSTED] Posts: 97 Joined: 3-April 08 From: Milling about Member No.: 29,596 |
My apologies for the delayed response.
The Compact and Repair utility is under tools the the Access menu. Access keeps sevral system tables in each DB that are hidden by default. One of these tables stores object level permissions. Thre system tables can get a bit wonky sometimes and need repaired. I am operating under the assumption that the DB is likely to have a mdw file as well given that it dies seem to have security enabled. The default location for this file is the same directory as the mdb file. Lastly you can certainly use VB to access an Access DB. You will, however, still need to have the database's username and password. |
|
|
|
May 11 2008, 11:28 AM
Post
#16
|
|
|
Super Member Group: [HOSTED] Posts: 713 Joined: 8-April 06 From: Lima - Peru Member No.: 12,579 |
My apologies for the delayed response. The Compact and Repair utility is under tools the the Access menu. Access keeps sevral system tables in each DB that are hidden by default. One of these tables stores object level permissions. Thre system tables can get a bit wonky sometimes and need repaired. I am operating under the assumption that the DB is likely to have a mdw file as well given that it dies seem to have security enabled. The default location for this file is the same directory as the mdb file. Lastly you can certainly use VB to access an Access DB. You will, however, still need to have the database's username and password. Thanks for your time and don't worry for your delayed response, as you can notice i just see your response because last month i had a lot of problems with my connection that fortunately i resolve a few days ago. I think that the better solution to this issue is by using VB to access this database. Best regards, |
|
|
|
![]() ![]() |
Similar Topics
|
Lo-Fi Version | Time is now: 5th July 2008 - 04:17 AM |