ACCdb vs ACCde question

[ChicagoPete]

So I have this simple db I created and one end-user wants to start entering
data BUT I know there will be changes coming to reports/queries/forms etc.

Do I allow just one user to run this as a ACCdb or do I create a ACCde?

If I create a ACCde then if I make changes to the ACCdb version on my test
pc and then overwrite the current ACCde, all newly entered data by the
end-user will be overwritten by my blank version of the ACCdb.

So how do you guys/gals handle this scenario - to upgrade a Access 2007 db
while it is in use? (Obviously, I would copy over the new code on the
weekend.)

Thanks for your opinions...

 

[Larry Daugherty]

First you split your application into a FrontEnd and a BackEnd. Look
in Access Help for Split. The BackEnd goes on a share that will map
to the same location from each eventual user's PC. Before
distributing the FrontEnd to your users (one copy to each user),
convert it into an ACCDE so that no design changes can be made. You
keep the only copies of the ACCDB and make your design changes there
before again converting a copy to ACCDE and rolling it out to your
users.

Find or google these Access newsgroups for FE Updater which if a free
utility provided by Tony Toews. That will tell you where you
eventually want to be.

HTH

 

[ChicagoPete]

Thanks Larry - just what I needed!

First you split your application into a FrontEnd and a BackEnd. Look
in Access Help for Split. The BackEnd goes on a share that will map
to the same location from each eventual user's PC. Before
distributing the FrontEnd to your users (one copy to each user),
convert it into an ACCDE so that no design changes can be made. You
keep the only copies of the ACCDB and make your design changes there
before again converting a copy to ACCDE and rolling it out to your
users.

Find or google these Access newsgroups for FE Updater which if a free
utility provided by Tony Toews. That will tell you where you
eventually want to be.

HTH

 

[Michel]

So I have this simple db I created and one end-user wants to start
entering
data BUT I know there will be changes coming to reports/queries/forms etc.

Do I allow just one user to run this as a ACCdb or do I create a ACCde?

If I create a ACCde then if I make changes to the ACCdb version on my test
pc and then overwrite the current ACCde, all newly entered data by the
end-user will be overwritten by my blank version of the ACCdb.

So how do you guys/gals handle this scenario - to upgrade a Access 2007 db
while it is in use? (Obviously, I would copy over the new code on the
weekend.)

Thanks for your opinions...

 

[gosta thorstrand]

You should separate all tables with data to a new database, link the tables to your application. Then it's easy to make changes in code, forms etc and overwrite the current application without loosing data.
My problem is that Access 2007.ACCde don't work but the same app in ACCdb works perfectly

Thank for your opininions about that