Conversion to 2007

[Charles via AccessMonster.com]

I have developed a database in 2003 and now I need to install it in a mixed
enviroment some PC have 2003 and some 2007 is there an easy way to make sure
everything works the way it was designed and what is the best way to make the
changes? I intend to have a front end and back end but install it on the same
shared network with desktop shortcuts.

Thanks

Charles

 

[Olduke]

While I have no experience in Access 07, I have had to put mixed Access
packages together in the past.
It is a total pain.
The back end is usually OK but the front ends require different programming
based on the differnt versions of VBA.
I don't know if Access 07 will even allow mixed usage in the tables. From
some of the complaints I've heard from 07 users, the answer may be no.
Perhaps you could put together a sample database in 03, put the back end on
the server and then see if it's compatable with 07 before you get into
anything more complex.
Good luck

 

[Rick Brandt]

While I have no experience in Access 07, I have had to put mixed
Access packages together in the past.
It is a total pain.
The back end is usually OK but the front ends require different
programming based on the differnt versions of VBA.

[snip]

I don't understand this statement. I create my apps in Access 97, convert a
copy to Access 2000 and between those two files can run under 97, 2000, 2002,
2003, and 2007 with no changes.

While there are a few quirks that have arisen in 2007 claiming that one needs
"different programming based on different versions of VBA" is quite a stretch.

Now if you do this backwards and design in the newest version using features
that older versions don't support (and then try to support users with those
versions anyway), then that is a different story. Of course that is just a bad
way to do it.

 

[Allen Browne]

Access 2007 can natively handle the Access 2000 or 2002/3 database formats,
so a well-designed database may work without modification in A2007.


However, the user interface is quite different in A2007 (e.g. ribbon in
place of menus and toolbars), and there are some compatibilitiy issues to be
aware of. For details, see:
Converting to Access 2007
at:
http://allenbrowne.com/Access2007.html


There are some properties you may want to set before you let the A2007 users
loose in this db:
Prevent Access 2007 users modifying existing databases
at:
http://allenbrowne.com/ser-69.html

The mixed front ends should be okay. As always, an MDE is best as it does
not decompile.

Don't miss the point about trusting the folder where the front end resides.

 

[Charles via AccessMonster.com]

Thanks to all for the good suggestions.

I'm always a bit hesitant to ask for help here because then I really get into
areas that I really do not understand.
Since I had no training or understand VBA I really don't know what a well
designed database is.
All I know Iis have multiple tables used to store data and multiple tables
for drop down menus in forms.
Sometime I used multiple queries to filter the information or shape reports
that I wanted.
It works very well but it was designed by using wizards and queries criteras.
During the 3 months since I discovered this site I have learned a lot of
things that would have done different from the beginning. So is it well
designed? I would venture to say no, but it works well, I was told it is user
friendly compared to other programs off the shelf. I was an opearation
manager and a user so I developed this out neccessity and used my experience
to makes the result usefull.
Next wednesday I will make it available to people that receaved new PC with
Office Pro 2007 and hope it will work as well with office 2003

Charles

Access 2007 can natively handle the Access 2000 or 2002/3 database formats,
so a well-designed database may work without modification in A2007.

However, the user interface is quite different in A2007 (e.g. ribbon in
place of menus and toolbars), and there are some compatibilitiy issues to be
aware of. For details, see:
Converting to Access 2007
at:
http://allenbrowne.com/Access2007.html

There are some properties you may want to set before you let the A2007 users
loose in this db:
Prevent Access 2007 users modifying existing databases
at:
http://allenbrowne.com/ser-69.html

The mixed front ends should be okay. As always, an MDE is best as it does
not decompile.

Don't miss the point about trusting the folder where the front end resides.

I have developed a database in 2003 and now I need to install it in a mixed
enviroment some PC have 2003 and some 2007 is there an easy way to make

[quoted text clipped - 4 lines]

same
shared network with desktop shortcuts.

 

[Allen Browne]

Fair enough, Charles.

If possible, it would be good if you could test it first, to make sure
things work as expected.

Limited VBA understanding does not mean you did not design it well, of
course. Sounds like you do have lookup tables for the dropdown lists, so
that's good: it hints that you do have an understanding of one-to-many
relationships which are the core of a good design.

All the best for the coming week.

--
Allen Browne - Microsoft MVP. Perth, Western Australia

Reply to group, rather than allenbrowne at mvps dot org.

Thanks to all for the good suggestions.

I'm always a bit hesitant to ask for help here because then I really get
into
areas that I really do not understand.
Since I had no training or understand VBA I really don't know what a well
designed database is.
All I know Iis have multiple tables used to store data and multiple
tables
for drop down menus in forms.
Sometime I used multiple queries to filter the information or shape
reports
that I wanted.
It works very well but it was designed by using wizards and queries
criteras.
During the 3 months since I discovered this site I have learned a lot of
things that would have done different from the beginning. So is it well
designed? I would venture to say no, but it works well, I was told it is
user
friendly compared to other programs off the shelf. I was an opearation
manager and a user so I developed this out neccessity and used my
experience
to makes the result usefull.
Next wednesday I will make it available to people that receaved new PC
with
Office Pro 2007 and hope it will work as well with office 2003

Charles

Access 2007 can natively handle the Access 2000 or 2002/3 database
formats,
so a well-designed database may work without modification in A2007.

However, the user interface is quite different in A2007 (e.g. ribbon in
place of menus and toolbars), and there are some compatibilitiy issues to
be
aware of. For details, see:
Converting to Access 2007
at:
http://allenbrowne.com/Access2007.html

There are some properties you may want to set before you let the A2007
users
loose in this db:
Prevent Access 2007 users modifying existing databases
at:
http://allenbrowne.com/ser-69.html

The mixed front ends should be okay. As always, an MDE is best as it does
not decompile.

Don't miss the point about trusting the folder where the front end
resides.

I have developed a database in 2003 and now I need to install it in a
mixed
enviroment some PC have 2003 and some 2007 is there an easy way to make

[quoted text clipped - 4 lines]

same
shared network with desktop shortcuts.