workfile secured db

[Guest]

I have a BE db secured by a workfile (I have the user/pwd). I need to link
tables in that db to my FE (unsecured). I am only reading this data - my main
BE data is also in a BE db (unsecured).

From the posts I have been reading, it would appear that there is no way to
simply link a table in the secured BE database... is that so? All I have read
so far says that I need to open each table (in the BE) as a recordset and
then copy all of the data in it into an array. Since the data in a couple of
the tables is rather large, I would like to avoid this if at all possible.

Any help? Thanks!

 

[Joan Wild]

I have a BE db secured by a workfile (I have the user/pwd). I need to link
tables in that db to my FE (unsecured). I am only reading this data - my
main
BE data is also in a BE db (unsecured).

I'm unclear why you have two backends. However, in the secure BE, can you
give the Users Group Open permission on the mdb, and read data permission on
the table(s)? They can then be read in the unsecure FE.

 

[Guest]

The secured BE is data from a different app - I have no control over it, I
only have permission to access its data for my app.

 

[Joan Wild]

How are *you* given permission? Can't you give your users the same?

 

[Guest]

I was given the workfile, the login, and the password of the db. If I use
their workfile (which I can't modify), doesn't that restrict my users to
read-only permissions in the FE? Or should create the same workfile with the
same user/login for my FE?

I tried using their workfile, but since I cannot give out the login/pwd, how
do I feed that information into the app so the user doesn't get a login
prompt?

 

[Joan Wild]

I was given the workfile, the login, and the password of the db. If I
use their workfile (which I can't modify), doesn't that restrict my
users to read-only permissions in the FE?

No the permissions are stored in the mdb, not the mdw.

I tried using their workfile, but since I cannot give out the
login/pwd, how do I feed that information into the app so the user
doesn't get a login prompt?

I think the only way would be to create a separate workspace in your
frontend and pass the username/password through that.

See section 46 of the security FAQ:
http://support.microsoft.com/?id=207793

 

[Guest]

Ok, I can do that - but then I have the problem of the login prompt.

I have to use the login/pwd given to me, but I am not allowed to give it to
the users. So, I can't let the users type them in and I can't put them in the
desktop shortcut as line switches because a user would be able to look at the
properties of the shortcut and see them.

Is there a way to hide the login/pwd values in the shortcut command line..?

Thanks!

 

[Joan Wild]

Ok, I can do that - but then I have the problem of the login prompt.

No you don't. It's handled in code (and you can create a MDE which won't
allow anyone to see the code).

See section 46 of the security FAQ:
http://support.microsoft.com/?id=207793

 

[Guest]

No - that code only allows me to open recordsets in the BE, it does not allow
me to link tables. If that code allowed linking tables, we wouldn't be having
this conversation

What I have to do is open my app using their workfile, with their login and
pwd. This lets me link tables in their BE. The only way to open my app with
their security is to put it into the shortcut command line, which exposes the
login/pwd to the user (if they were to look in the shortcut properties).

So, to open my app, I need the shortcut to run a script (which is a separate
compiled mde) which launches the Shell command that opens my app with the
user/pwd switches set (this hides the login/pwd from the user), like this:

strPathToAccess = SysCmd(acSysCmdAccessDir) & "runaccess.EXE"
Shell (strPathToAccess & " /excl /runtime /wrkgrp " & """Workfile.mdw""" &
" /user " & """userval""" & " /pwd " & """pwdval""" & " " &
"""AppFile.mde"""), vbMaximizedFocus
Application.Quit

 

[Joan Wild]

So, to open my app, I need the shortcut to run a script (which is a
separate compiled mde) which launches the Shell command that opens my
app with the user/pwd switches set (this hides the login/pwd from the
user), like this:

Glad you got it working.