Packaging and Security

  • Thread starter Thread starter Connie
  • Start date Start date
C

Connie

I have packaged a split database joined to a specific
security workgroup. When installed on a computer without
Access, the workgroup can't be joined and no matter what
I attempt in the packaging process, nothing works.

In all of the materials researched, nothing discusses
packaging a secured database?

Any suggestions much appreciated.


Connie
 
In all of the materials researched, nothing discusses
packaging a secured database?
Click to expand...

You need to submit either the mdw that you secured the database with, or
create a new one with the appropriate users, passwords and PINs.

However you access the database, you'll need to specify the appropriate
workgroup file when opening it in its workspace. Check the documentation
for DBEngine and Workspace objects, if you are using DAO. There will be
something similar if you have to use ADO (but it's a crappy way of
attaching to Jet databases anyway).

HTH


Tim F
 
I have found lots of data on security, and lots on
packaging but none on packaging a secured database. I
took a quick look at the documenation you suggest. Not
sure yet it that is the answer I seek.

To clarify, I want to use a security workgroup that we
have already created for the database. The database has
been joined to that workgroup. When I packaged it, this
workgroup was included with the dependency files. A path
was set so that the main file would find it. However,
when the package is installed on a pc or laptop that does
not have Office Access, access to the database is denied
saying "you don't have permission..."etc. I don't know
of a way, if any exists, of "specifying the appropriate
workgoup file" on a computer without Access installed.
Do you know a way to do this in such a scenario or am I
missing something in my packaging?
 
Well, of course you use a shortcut to launch the application. And of course
in that shortcut you do specify your work group file?

If you have been developing long enough to the point of getting ready to
distribute an application, then I am sure you realize that it is terrible to
try and change the default workgroup on SOME ONE ELSE'S COMPUTER? Forget
that. That would mean that every other access application would now force
the user to get a logon prompt (you customers will kill you!). No way would
I install something that changes my default security workgroup file. You
don't need to have your users join the security workgroup, you simply
provide the workgroup name in the shortcut that launches the application.

So, the solution here is simple: you set the workgroup file in the shortcut
that you provide to launch the application.

I suspect there is not much info on this since it is um-imagine that you are
at the point of getting ready to distribute an application, but don't
realize how horrible and bad it would be to switch the users default
security group? What will happen if the users already have a workgroup set
for their existing appcltions?

Since I develop many different application for many different people, then
again each of my many projects of course thus uses its own security
workgroup (usually in the same dir along with the application).

If you are providing a shortcut, you will get something like:

"C:\Program Files\Microsoft Office\Office\msaccess.exe"
"c:\program files\Rides\Rides.mdb"
/wrkgrp "c:\Program Files\Rides\Ridesec.mdw"

In each of my work directories, I also put in a quick launch shortcut so I
don't have to type in the password during development (who wants to get a
stupid logon prompt all day?). So I often uses:

"C:\Program Files\Microsoft Office\Office\msaccess.exe"
"c:\program files\Rides\Rides.mdb"
/wrkgrp "c:\Program Files\Rides\Rides.mdw"
/User "RidesAdmin" /pwd "MyPassWord"


For all other databases, I simply don't use a shortcut, and thus I just use
the default workgroup file, and again I don't get any annoying logon prompts
for un-secured databases. I mean, what do you do in this case? Do you live
with logon prompts for all your databases when all of them are not secured?
Why?
 
I have obviously asked the wrong people for help. Your
attitude needs adjustment. This conversation is over!
 
Thanks for the response Tim. I fully understand the
implications of changing the default workgroup and this
was not my intention. Prior to beginning the packaging
process, I joined the specific database with the
appropriate workgroup and created a shortcut with the
necessary switches. At packaging time, I included and
pointed the shortcut to the desktop and still this did
not work. I have tried several different things and
nothing seems to work. I get the same message ...You do
not have permission... Upon further reading, others have
had, (if not similar), problems with the pdwiz. If these
people are to be believed, you need additional software
to make the packaging work.

Connie
 
Back
Top