Access 97

  • Thread starter Thread starter Evan
  • Start date Start date
E

Evan

I created a back end database some years ago which was quite secure but as
time passed and usages spread essentially swicthed security off by allowing
all "Users" essentially full permission (Open db, read, write, delete edit
data in tables etc). Let's call this BE

A lot of this was due to the absolute pain using Crystal OCX in VB progs on
a secure Access db!.

Anyway, have now linked a table from the secure backend (BE) into another
mdb (FE). This front end was created using default permissions. If you open
up that db (FE) using default access you can read the data fine in the
linked table from BE fine.

But we use another application that connects via ODBC to the FE database.
When that application tries to access data in the linked table from BE it
says "No read permissions"

Any ideas?

TIA

Evan
 
-----Original Message-----
I created a back end database some years ago which was quite secure but as
time passed and usages spread essentially swicthed security off by allowing
all "Users" essentially full permission (Open db, read, write, delete edit
data in tables etc). Let's call this BE

A lot of this was due to the absolute pain using Crystal OCX in VB progs on
a secure Access db!.

Anyway, have now linked a table from the secure backend (BE) into another
mdb (FE). This front end was created using default permissions. If you open
up that db (FE) using default access you can read the data fine in the
linked table from BE fine.

But we use another application that connects via ODBC to the FE database.
When that application tries to access data in the linked table from BE it
says "No read permissions"

Any ideas?

TIA

Evan

Check your securities. Be sure the "read" permissions are
granted on tables and so on. This will also require to
password the Admin account to have a log on. With out this
you will not be able to instate these permissions. This
will require a new work group admin. This should be you.
Make sure you grant a new "group" with all permissions and
change the ownership to your account. Remember to write
all this information down and keep it in a safe place. I
all you must make your application secure and use your own
work group with all p.i.n.s and passwords. To relay get it
going you should password out the database also. When you
go from your link the log on logo will show and you will
simply log on. Now you will have effective permissions
granted to do as you wish.

Ricky J. Pyzynski
Data Bases ETC
 
Back
Top