Re: security with system.mdw

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance



Your post will be looked at by others that run into the same issue, and your
solution will help them out. No reason at all to feel badly!!


--
Rick B



"LCalaway" <lcalaway@xxxxxxxxxx> wrote in message
news:OUC9f.1865$0d.128@xxxxxxxxxxx
>I have just answered my own question.
>
> I didn't understand that I had omitted a fact that is so central: The
> passwords were added AFTER the databases were linked.
>
> To make everything work right, I deleted the links and relinked the now
> passworded tables.
> I feel really dumb.
>
> Thank you for listening.
>
> LCalaway
>
>
> "LCalaway" <lcalaway@xxxxxxxxxx> wrote in message
> news:dFA9f.549$0d.319@xxxxxxxxxxx
>> Hello all:
>>
>> I have the following database structure:
>> Front End Application
>> Back End Application
>> No special mdw file was created.
>> Everyone is Admin
>>
>> I am trying to secure the databases at the lowest level -- just a single
>> password to enter. Everyone who uses the application has complete access
>> to everything.
>>
>> I put the same password on each database via "Set database password" in
>> Security.
>>
>> The front end database opens okay using the password. When attempting to
>> access the data in the tables in the back end through the front end,
>> however, I get the following message: "There was an error executing the
>> command."
>>
>> If I remove the password from the backend, everything works fine.
>>
>> Am I trying to do something that cannot be done so easily?
>>
>> Thank you
>>
>> LCalaway
>>
>>
>>
>
>


.



Relevant Pages

  • Re: security with system.mdw
    ... > I have the following database structure: ... > No special mdw file was created. ... > Everyone is Admin ... > LCalaway ...
    (microsoft.public.access.security)
  • compiler and metadata, request opinions...
    ... a lot of the upper/middle compiler machinery is still lacking (such as ... embed the metadata directly into the object modules (the reason being that ... request for a particular piece of information is embedded in a symbol (sort ... it will be loaded into an in-memory version of the database. ...
    (comp.compilers)
  • misc: compiler and metadata...
    ... a lot of the upper/middle compiler machinery is still lacking (such as ... embed the metadata directly into the object modules (the reason being that ... request for a particular piece of information is embedded in a symbol (sort ... it will be loaded into an in-memory version of the database. ...
    (comp.lang.misc)
  • RE: how to list LE options
    ... for whatever reason an applications programmer has to look at this ... curiousity and desire to expand their knowledge, there is no real reason ... LE options were copied to an application parmlib, ... There's no reason that Database, CICS and other groups can't maintain ...
    (bit.listserv.ibm-main)
  • RE: [dbi] RE: Accessing MS Access through the DBI ODBC
    ... reason for this issue is the mdb is on a mapped drive where the mapped driver ... > still getting 'Unable to connect to database'. ... > use DBI; ... Then it will simply display it and die since there ...
    (perl.dbi.users)