Stuck understanding security

[Naz]

Hi

I'm trying to implement ULS in a database that i have set-up but am really
stuck. I'm using Access 2003, the database is unsecure at the moment but is
split FE and BE, its sits on the shared folder on the server, and has been
published as a run-time by our IT team so everyone can access it. Everytime i
want to make development chages to the FE i just overwrite the old file with
the new file and the puiblished run-time version works. I don't know much
about run-times.

Now i can just about secure a normal database on my C drive, but from
everything that i have read. After a database is made secure you no longer
access it from the original file, you use a shortcut, defining the location
of the MDB and the associated MDW securty workgroup file. But if i replace
the original file with a short-cut the run-time doesn't work.

Is there a way of getting the database to associate itself with the correct
MDW on opening, rather than needing the shortcut?

Any help would be greatly appreciated.

 

[Rick Brandt]

Hi

I'm trying to implement ULS in a database that i have set-up but am
really stuck. I'm using Access 2003, the database is unsecure at the
moment but is split FE and BE, its sits on the shared folder on the
server, and has been published as a run-time by our IT team so
everyone can access it. Everytime i want to make development chages
to the FE i just overwrite the old file with the new file and the
puiblished run-time version works. I don't know much about run-times.

Now i can just about secure a normal database on my C drive, but from
everything that i have read. After a database is made secure you no
longer access it from the original file, you use a shortcut, defining
the location of the MDB and the associated MDW securty workgroup
file. But if i replace the original file with a short-cut the
run-time doesn't work.

Of course it does. It just has to be a shortcut that points to the MSAccess
executable that is installed by the runtime. That executable by the way, is
absolutely no different from "normal" Access other than its location on the
hard drive. If you were trying to just copy your shortcut to a user's PC
with the runtime then it is simply pointing to the wrong location. The
target of the shortcut needs to look like...

"Path to MSAccess.exe" /wrkgrp "Path to MDW" "Path to MDB"

Is there a way of getting the database to associate itself with the
correct MDW on opening, rather than needing the shortcut?

Users can be pointed at an MDW either by making it their default (joining
it) or by use of a shortcut as you mentioned. MDB files cannot be
associated with an MDW file.

 

[Naz]

Hi Rick,

Thanks for your response.....but unfortunately i am none the wiser.

Without really understanding too much about the runtime issue the first
hurdle that i see is that the shorcut

"Path to MSAccess.exe" /wrkgrp "Path to MDW" "Path to MDB"

refers to the location of MS Access unfortunate (not thought to mention in
my OP) we use MS Access as a published app shortcut....so there is no
directory...it just a shortcut that refers to a Citrix ICA thingy. Works fine
on a PC with Access installed as a proper app, but that PC is the exception.

Any thoughts anyone?

 

[Rick Brandt]

Hi Rick,

Thanks for your response.....but unfortunately i am none the wiser.

Without really understanding too much about the runtime issue the
first hurdle that i see is that the shorcut

"Path to MSAccess.exe" /wrkgrp "Path to MDW" "Path to MDB"

refers to the location of MS Access unfortunate (not thought to
mention in my OP) we use MS Access as a published app shortcut....so
there is no directory...it just a shortcut that refers to a Citrix
ICA thingy. Works fine on a PC with Access installed as a proper app,
but that PC is the exception.

Any thoughts anyone?

If you are running the app over Citrix then the published app on Citrix has
to be a batch file that launches the Access app using the same path with
arguments as the shortcut example I gave you.

 

[yaala]

Hi

I'm trying to implement ULS in a database that i have set-up but am really
stuck. I'm using Access 2003, the database is unsecure at the moment but
is
split FE and BE, its sits on the shared folder on the server, and has been
published as a run-time by our IT team so everyone can access it.
Everytime i
want to make development chages to the FE i just overwrite the old file
with
the new file and the puiblished run-time version works. I don't know much
about run-times.

Now i can just about secure a normal database on my C drive, but from
everything that i have read. After a database is made secure you no longer
access it from the original file, you use a shortcut, defining the
location
of the MDB and the associated MDW securty workgroup file. But if i
replace
the original file with a short-cut the run-time doesn't work.

Is there a way of getting the database to associate itself with the
correct
MDW on opening, rather than needing the shortcut?

Any help would be greatly appreciated.

--

_______________________
Naz,
London