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
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