After splitting the backend has no security?

  • Thread starter Thread starter Ed
  • Start date Start date
E

Ed

I have created several Access db apps, but I'm in the
process of utilizing security for the first time. I used
User-Level security and the process seemed relatively
straightforward. However, now them I'm ready to deploy, I
ran the database splitter and learned that my backend db
is wide open with no security. For a newbie to security,
what's the most efficient way to solve this issue. Thanks.
 
Ed said:
I have created several Access db apps, but I'm in the
process of utilizing security for the first time. I used
User-Level security and the process seemed relatively
straightforward. However, now them I'm ready to deploy, I
ran the database splitter and learned that my backend db
is wide open with no security. For a newbie to security,
what's the most efficient way to solve this issue. Thanks.
Click to expand...

Forget the splitter tool. If you make a copy of your combined file and
delete everything but tables from one and delete just the tables from the
other, then link the tables in the former to the latter, then you
accomplish the same thing as the splitter, but don't lose your security.
Better yet would be to start out split from the get-go.
 
Better yet would be to start out split from the get-go.
Though the idea is quite good one,while developing it can
be a pain,especially if you need to make some changes in
the table.you will have to keep flitting between 2 db's,
the Fe and the BE
 
Back
Top