Re: Microsoft Access Table Security
- From: Kax <carlm@xxxxxxxx>
- Date: Mon, 14 Jul 2008 04:19:13 -0700 (PDT)
On Jul 12, 12:46 pm, Tom van Stiphout <no.spam.tom7...@xxxxxxx> wrote:
On Sat, 12 Jul 2008 07:39:17 -0700 (PDT), Kax <ca...@xxxxxxxx> wrote:
Now you're starting to make sense :-)
Upsizing 4 tables to sqlserver (perhaps even the free Express edition)
and pointing the ODBC driver to it will take less than 15 minutes. I
would try that right away.
<clip>
**PS: I say temporarily because the very next step for us is to
convert the data and application to run from SQL server. Then all of
these security issues go away. Should I punt attempting to secure
Access for my purposes?- Hide quoted text -
- Show quoted text -
Thanks for the response! THe problem is that this MDB sits in a
process and is used by several applications. Converting the apps over
takes a bit more time then we need to set up SQL2005 on a virtualized
server put the other apps on another virtual server and then ship it
out. My problem isn't finding the best method (or at least a pretty
decent one) but my problem is time. I need to get this out today or
tomorrow...then I'll have a couple weeks to get the better solution up
and running. I bought Garry Robinson's "Real World Microsoft Access
Database Projection and Security" and it looks like it might be able
to me through this. I don't need (or expect) the security of the big
dog databases for the next couple of weeks...just enough to be a
deterrent until I can get the MsSQL system out there.
.
- References:
- Re: Microsoft Access Table Security
- From: Tom van Stiphout
- Re: Microsoft Access Table Security
- Prev by Date: Re: sending password-protected data/reports on emails with Access 2000
- Next by Date: student
- Previous by thread: Re: Microsoft Access Table Security
- Next by thread: Re: Security
- Index(es):
Relevant Pages
|
