Using CodeDB 1

[SBendBuckeye]

Let's say I want to put a CodeDB on drive T which is an IS/IT development drive. I want to give UserA access to it and they run from drive L. Also, UserB runs from drive R.

Are there any permission issues that need to be resolved before using the CodeDB (eg will UserA or UserB get no access errors when CodeDB on drive T is called)?

Thanks for the help!

 

[FancyPrairie]

I'm assuming you're talking about a library database. Regardless, you don't want to reference the library by drive letters. Rather, use share names (i.e. \\server\shareName\LibraryName). Your technical people can setup a share for you (real simple), if you don't know how to do it. The share properties can be set so that only certain users have access to the folder.

 

[SBendBuckeye]

Thanks FancyPrairie! Just to make sure I understand you correctly, are you saying that users would need to be given read only access to drive T where the CodeDB resides to be able to use the front end which refers to it?

If so, can this be done in code to avoid helpdesk issues? Obviously, the front end will be installed where the user already has access. I would rather the user not have to remember to do one additional thing to use the app.

Thanks again for you help!

 

[FancyPrairie]

The user's need the rights to be able to read and update tables in your database. You don't want them to be able to add files or delete files from the folder where the library routine resides.

For this to work, the users don't have to do anything. In the code view window, select Tool|References... and browse to your library routine and select it. But when you browse, use the share name (i.e. \\server\share\yourlibrarydb.mdb) not a drive letter (i.e. t:\folder\youlibrarydb.mdb). Now, when you want to give a new user a copy of your database, you will need to copy your database (not the library db) to the user's machine and make sure they have access to the share (because your database references a library database on that share).

 

[SBendBuckeye]

Thanks for the followup. I'll give that a try next week.