Some questions about a deployed/packaged DB

[yus786]

Hi

Using the Access 2007 Developer Extensions and Runtime, i have deployed one of my 2007 db. Just a couple of questions:

1. Once the users 'installs' the package, is the DB fairly secure? I mean could the users shift and open to get to the backend? I did try myself and couldn't shift open but just want to make sure

2. If i need to make changes to it - how do i go about this? How do i convert this back to a accdb format?

Thanks

 

[Rabbie]

In answer to question 2 the answer is you can't. You need to keep a copy of your accdb database and make changes to that and then convert it. The conversion process will leave your accdb copy

 

[yus786]

Thanks

But is it secure?

 

[boblarson]

Thanks

But is it secure?

Access is not secure. You can take steps to keep the casual users out but if someone knows what they are doing they can get in. If you need to keep the data secure and non-portable, you will need to use a different backend. SQL Server 2008 Express is a good one to use because you can limit users to what they can see and do with the data just like you can with the full version of SQL Server. The Express version is good because it can hold up to 10 Gb of data (compared to Access which can do 2 Gb) and you can have groups set up so that certain groups can have access to certain data or execution privileges and more.

 

[yus786]

In answer to question 2 the answer is you can't. You need to keep a copy of your accdb database and make changes to that and then convert it. The conversion process will leave your accdb copy

After your opinion here.

Say i send the user a packaged db and say 6 months down the line, they find an issue with something (anything). Usually i would request the DB back, open it up, replicate the issue and then try to fix it.

How would one deal with this if it's packaged?

 

[boblarson]

After your opinion here.

Say i send the user a packaged db and say 6 months down the line, they find an issue with something (anything). Usually i would request the DB back, open it up, replicate the issue and then try to fix it.

How would one deal with this if it's packaged?

1. If there is a backend problem you will need to figure out how to fix it and then implement the changes without losing data. There isn't a hard and fast rule about this. You would need to do something based on the situation.

2. If it is just a frontend update you can just send them the new frontend to put in place; no package needed. If you have supporting files that need to go, then you might need to package it up but for most applications that isn't necessary.