Splitting a database/securing it

[Guest]

Hello everyone,

I am using Access 2003 to construct a database for work. This database will
be used by multiple people, so I was going to split the database (putting the
BE on the network server and the FE on each pc). This is my first time under
going this process, so bear with me.

I have three questions. First, my job has Access 2000 and I have not
entered all of my data into the BE yet----Can I install the BE into the
server and still enter data at work, while I work on the FE at home? I know
Access defaults to 2000 format, but does the server have to have Access 2003?

Also the database must be secured, I don't know how to secure a database
with multiple users? How do I do this?

Chantel.

 

[Kevin3NF]

The only way data can get from your workstation at home to the back-end at
the offfice is if you are connected to the office via the internet or a VPN.
In either case, it is very likely going to be so slow it will feel unusable.
Even as fast cable connection is significantly slower than your office LAN

Access has built-in security, but it is limited and hackable by anyone with
the ability to search Google and download a Access cracking tool. If
security is a must, you might want to consider moving up to MSDE (light
version of SQL Server) and using the built-in security of that product.

--
Kevin Hill
President
3NF Consulting

www.3nf-inc.com/NewsGroups.htm

 

[Guest]

The database was constructed and split from my home computer. I saved the BE
file to a CD and was going to install the data on server at work. Will this
work?

I'm not a developer, so getting into the world of servers is unfamiliar
territory. I thought that SQL was used in Access, how is this MSDE any
different? Is this a language the server must have or is this a software
that I must buy?

Chantel.

 

[Kevin3NF]

SQL is the language used to query and manipulate data

SQL Server is a database product made by Microsoft. So is Access. They
both use the SQL language under the hood.

MSDE is a scaled down version of SQL Server.

In a split arrangement, the data (BE) resides in one and only one place (the
server). Users have the Front-end on their workstations and connect to the
BE via linked tables (in your current setup, which is an Access file for
both ends)

If you try to use your existing setup from home, the FE is at your house and
the BE is at the office. The internet connection between the two is very
slow and prone to dropping out (which you may not even see). It will be
hard to usse and higly suceptible to corruption due to the unstable internet
connection.

Please ask for more clarification. Like a bad comedian, "I'm here all week"

--
Kevin Hill
President
3NF Consulting

www.3nf-inc.com/NewsGroups.htm

 

[MacDermott]

Perhaps you could elaborate a little on your need to "secure" the database.
If you just need a system to keep well-intentioned users from making
mistakes, Access security will do fine.
If you're dealing with sensitive data likely to be attacked by determined
hackers, Kevin is correct - Access security is not up to the task.
And in answer to your question about MSDE, yes, it would have to be
running on the server. Access uses a file server approach; the server where
the back end resides doesn't need to run any special software. In contrast,
MSDE uses a client-server approach.
Of course, if your front end remains in Access, it remains vulnerable to
hackers. And depending on how you structure your connection to the back
end, this could give hackers a route to your data...

 

[Guest]

Yes, it is sensitive data.

I'm still confused, I think. I'm assuming that if I want a very secured
database, I must change from a file server approach (Access) to a client
server approach (MSDE). The BE, eventhough constructed using Access, is not
a problem however; the FE must be changed to MSDE software. Is this correct?
If so, does this mean I have to start from scratch? If it is a matter of
just converting from Access to MSDE, will my user interface forms + code
still be intacted?

Chantel.

 

[Guest]

Actually, I do not intend to link my FE from home. I am still designing
forms, but when completed I was going to save the CD to install on each pc at
work. My office is being renovated, so a lot of my work is done at home
(just so I can meet the deadline).

Do I have to change my entire Access database to MSDE in order to have a
very secure database or just the front end? If so, how do I do that? I
really want my user interface forms to be intacted?

Chantel.

 

[Kevin3NF]

2nd thing 1st:
MSDE is the data only....you cannot make a front-end out of MSDE. The FE
will stay in Access.
Access by itself is really just a file and every bit as easy to crack as a
password protected Word file. You can do some things to slow people down,
but a determined person can easily find everything they need on the internet
in just a few minutes.

re: designing forms at home...

The forms will not work without a connection to the tables. If this is for
development only, have a copy of the back-end at home to develop against and
you're in good shape. If you want to do data-entry/production work at home
as well as development, then you either have to suffer the lag over the
internet, or find a way to synch two back-ends....

--
Kevin Hill
President
3NF Consulting

www.3nf-inc.com/NewsGroups.htm

 

[Kevin3NF]

You've got it backwards...but you're getting there

back-end is in MSDE. MSDE has stronger security features, and this is where
the data is. The data is (presumably) what you really want to secure.

Access tables convert to MSDE tables reasonably well with a few tweaks here
and there. Once they are done, you will need to create a DSN on each client
machine and link the FE to the MSDE BE through that connection. This part
is way easier than it sounds.

If you think you may be in over your head, please click my link below for
ways to reach me.

Or, keep asking questions until you are comfortable...

--
Kevin Hill
President
3NF Consulting

www.3nf-inc.com/NewsGroups.htm

 

[MacDermott]

So you have this "secure" data in a MSDE database, and an Access front end
which links to it.
Someone goes on the Internet and downloads an Access security-cracker, with
which he opens the Access front end. Now how secure is your MSDE data?

 

[Rick Brandt]

So you have this "secure" data in a MSDE database, and an Access
front end which links to it.
Someone goes on the Internet and downloads an Access
security-cracker, with which he opens the Access front end. Now how
secure is your MSDE data?

If security is applied in the MSDE database then only a person who has MSDE
autorities will be able to manipulate data with the Access file. Anyone else
will just get ODBC errors.

This assumes of course that you do NOT embed the passwords in the links or code.
Either use trusted connections or connections that force the user to log in.