Using 2003 db in 2007

[Jeff]

This is something I can't test (don't have 2007) and found no definitive
answer, but a few conflicting ones.

Will a 2003 database work correctly in Access 2007?

Don't want to do any design work, just execute and use the database in 2007.

And will Office and Access 2003 work correctly in Vista?

Jeff
"More Access Stuff."
http://www.asken.com.au

[Allen Browne]

Hi Jeff.

I'll give you a qualified "Yes" as the answer to this question.
Yes: A2007 can natively use databases in the 2000 or 2002/3 file format,
but...

a) The user will have to get used to the ribbon instead of menus and
toolbars. If you used custom toolbars, they will appear as an option on the
ribbon, so the interface may not be as you expect. You'll need to explore
this to check that this is okay.

b) There are some bugs in A2007 that mean most of my database don't work
properly. For example, if you use Report_Open to assign the Control Source
of controls in a report (fairly common with crosstabs etc), attempting to
open this report will crash Access 2007. List of things to check:
http://allenbrowne.com/Access2007.html#Bugs

c) You might want to check this out:
Prevent Access 2007 users modifying existing databases
at:
http://allenbrowne.com/ser-69.html
You can use Access 2003 to run the code. It does stuff like creating the
properties that block layout view, and prevent users from making schema
changes in datasheets (such as renaming or adding fields on the fly.)

--
Allen Browne - Microsoft MVP. Perth, Western Australia
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"Jeff" <no******@asken.com.auwrote in message
news:46***********************@per-qv1-newsreader-01.iinet.net.au...

This is something I can't test (don't have 2007) and found no definitive
answer, but a few conflicting ones.

Will a 2003 database work correctly in Access 2007?

Don't want to do any design work, just execute and use the database in
2007.

And will Office and Access 2003 work correctly in Vista?

Jeff
"More Access Stuff."
http://www.asken.com.au

[Jeff]

Hi Allen

I don't have any custom menus or toolbars, generally, so only a problem with
select databases.

'b' may be an issue. I will have to check the code. Been a while since I
wrote it.

The databases are usually delivered as MDEs and users understand they are
not to modify anything that can be modified (I say jokingly). Are earlier
version MDEs a problem at all in 2007.

What about developing in 2003 in Vista? I think I remember you saying before
that this is okay.
"Allen Browne" <Al*********@SeeSig.Invalidwrote in message
news:46***********************@per-qv1-newsreader-01.iinet.net.au...

Hi Jeff.

I'll give you a qualified "Yes" as the answer to this question.
Yes: A2007 can natively use databases in the 2000 or 2002/3 file format,
but...

a) The user will have to get used to the ribbon instead of menus and
toolbars. If you used custom toolbars, they will appear as an option on
the ribbon, so the interface may not be as you expect. You'll need to
explore this to check that this is okay.

b) There are some bugs in A2007 that mean most of my database don't work
properly. For example, if you use Report_Open to assign the Control Source
of controls in a report (fairly common with crosstabs etc), attempting to
open this report will crash Access 2007. List of things to check:
http://allenbrowne.com/Access2007.html#Bugs

c) You might want to check this out:
Prevent Access 2007 users modifying existing databases
at:
http://allenbrowne.com/ser-69.html
You can use Access 2003 to run the code. It does stuff like creating the
properties that block layout view, and prevent users from making schema
changes in datasheets (such as renaming or adding fields on the fly.)

--
Allen Browne - Microsoft MVP. Perth, Western Australia
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"Jeff" <no******@asken.com.auwrote in message
news:46***********************@per-qv1-newsreader-01.iinet.net.au...

>This is something I can't test (don't have 2007) and found no definitive
answer, but a few conflicting ones.

Will a 2003 database work correctly in Access 2007?

Don't want to do any design work, just execute and use the database in
2007.

And will Office and Access 2003 work correctly in Vista?

Jeff
"More Access Stuff."
http://www.asken.com.au

[Keith Wilby]

"Allen Browne" <Al*********@SeeSig.Invalidwrote in message
news:46***********************@per-qv1-newsreader-01.iinet.net.au...

Hi Jeff.

I'll give you a qualified "Yes" as the answer to this question.
Yes: A2007 can natively use databases in the 2000 or 2002/3 file format,
but...

a) The user will have to get used to the ribbon instead of menus and
toolbars. If you used custom toolbars, they will appear as an option on
the ribbon, so the interface may not be as you expect. You'll need to
explore this to check that this is okay.

b) There are some bugs in A2007 that mean most of my database don't work
properly. For example, if you use Report_Open to assign the Control Source
of controls in a report (fairly common with crosstabs etc), attempting to
open this report will crash Access 2007. List of things to check:
http://allenbrowne.com/Access2007.html#Bugs

c) You might want to check this out:
Prevent Access 2007 users modifying existing databases
at:
http://allenbrowne.com/ser-69.html
You can use Access 2003 to run the code. It does stuff like creating the
properties that block layout view, and prevent users from making schema
changes in datasheets (such as renaming or adding fields on the fly.)

On the ball as always Allen. I didn't know that A2007 had these "features"
and will use your code to turn them off. Many thanks.

Keith.

[Keith Wilby]

"Allen Browne" <Al*********@SeeSig.Invalidwrote in message
news:46***********************@per-qv1-newsreader-01.iinet.net.au...

Hi Allen,

I just noticed this in the code:

'Limits: Not designed for secured or replicated databases.

Could you expand on that with respect to ULS please?

Thanks again.

Keith.

[Allen Browne]

Yes: developing in 2003 on Vista is fine.

I suggest you create your own shortcut to msaccesse.exe, and check the box
for:
Run As Administrator
so you don't run into this kind of problem:
Errors using multiple versions of Access under Vista
at:
http://allenbrowne.com/bug-17.html

--
Allen Browne - Microsoft MVP. Perth, Western Australia
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"Jeff" <no******@asken.com.auwrote in message
news:46***********************@per-qv1-newsreader-01.iinet.net.au...

Hi Allen

I don't have any custom menus or toolbars, generally, so only a problem
with select databases.

'b' may be an issue. I will have to check the code. Been a while since I
wrote it.

The databases are usually delivered as MDEs and users understand they are
not to modify anything that can be modified (I say jokingly). Are earlier
version MDEs a problem at all in 2007.

What about developing in 2003 in Vista? I think I remember you saying
before that this is okay.
"Allen Browne" <Al*********@SeeSig.Invalidwrote in message
news:46***********************@per-qv1-newsreader-01.iinet.net.au...

>Hi Jeff.

I'll give you a qualified "Yes" as the answer to this question.
Yes: A2007 can natively use databases in the 2000 or 2002/3 file format,
but...

a) The user will have to get used to the ribbon instead of menus and
toolbars. If you used custom toolbars, they will appear as an option on
the ribbon, so the interface may not be as you expect. You'll need to
explore this to check that this is okay.

b) There are some bugs in A2007 that mean most of my database don't work
properly. For example, if you use Report_Open to assign the Control
Source of controls in a report (fairly common with crosstabs etc),
attempting to open this report will crash Access 2007. List of things to
check:
http://allenbrowne.com/Access2007.html#Bugs

c) You might want to check this out:
Prevent Access 2007 users modifying existing databases
at:
http://allenbrowne.com/ser-69.html
You can use Access 2003 to run the code. It does stuff like creating the
properties that block layout view, and prevent users from making schema
changes in datasheets (such as renaming or adding fields on the fly.)

"Jeff" <no******@asken.com.auwrote in message
news:46***********************@per-qv1-newsreader-01.iinet.net.au...

>>This is something I can't test (don't have 2007) and found no definitive
answer, but a few conflicting ones.

Will a 2003 database work correctly in Access 2007?

Don't want to do any design work, just execute and use the database in
2007.

And will Office and Access 2003 work correctly in Vista?

Jeff
"More Access Stuff."
http://www.asken.com.au

[Allen Browne]

Hi Keith

It's just details like the PrepareAllFor2007() function performs the changes
on all databases that meet a filespec in a folder, and it doesn't know how
the username, password and mdw to use for each one, so the OpenDatabase()
will fail on a secured database.

Similarly, if you are not logged into the current database with admin
rights, the attempt to create/set properties might not work.

If it doesn't error, it probably created the properties successfully. Easy
enough to test.

--
Allen Browne - Microsoft MVP. Perth, Western Australia
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"Keith Wilby" <he**@there.comwrote in message
news:46**********@glkas0286.greenlnk.net...

"Allen Browne" <Al*********@SeeSig.Invalidwrote in message
news:46***********************@per-qv1-newsreader-01.iinet.net.au...

Hi Allen,

I just noticed this in the code:

'Limits: Not designed for secured or replicated databases.

Could you expand on that with respect to ULS please?

Thanks again.

Keith.

[Keith Wilby]

"Allen Browne" <Al*********@SeeSig.Invalidwrote in message
news:46***********************@per-qv1-newsreader-01.iinet.net.au...

Hi Keith

It's just details like the PrepareAllFor2007() function performs the
changes on all databases that meet a filespec in a folder, and it doesn't
know how the username, password and mdw to use for each one, so the
OpenDatabase() will fail on a secured database.

Similarly, if you are not logged into the current database with admin
rights, the attempt to create/set properties might not work.

If it doesn't error, it probably created the properties successfully. Easy
enough to test.

Ah right, so as long as I run the code on the current db I should be OK.
Many thanks Allen.

[Jeff]

I am thinking of getting a basic box to install 2003. I looked at a HP
Pavilion (not my fav brand) with just 512mb, 1.66 MHz dual and think it will
be okay. Maybe upgrade to 1 GB mem. But it only comes with Vista hence the
Vista question. At $598 (no monitor) seems a good price.

I will then use a KVM switch to switch between 3 system I have under my
desk.

So only one version on each box. Seems simpler for me and and outlay of $650
including the switch seems a bargain.

Just not yet convinced the box will run Vista and 2003 well.

"Allen Browne" <Al*********@SeeSig.Invalidwrote in message
news:46***********************@per-qv1-newsreader-01.iinet.net.au...

Yes: developing in 2003 on Vista is fine.

I suggest you create your own shortcut to msaccesse.exe, and check the box
for:
Run As Administrator
so you don't run into this kind of problem:
Errors using multiple versions of Access under Vista
at:
http://allenbrowne.com/bug-17.html

--
Allen Browne - Microsoft MVP. Perth, Western Australia
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"Jeff" <no******@asken.com.auwrote in message
news:46***********************@per-qv1-newsreader-01.iinet.net.au...

>Hi Allen

I don't have any custom menus or toolbars, generally, so only a problem
with select databases.

'b' may be an issue. I will have to check the code. Been a while since I
wrote it.

The databases are usually delivered as MDEs and users understand they are
not to modify anything that can be modified (I say jokingly). Are earlier
version MDEs a problem at all in 2007.

What about developing in 2003 in Vista? I think I remember you saying
before that this is okay.
"Allen Browne" <Al*********@SeeSig.Invalidwrote in message
news:46***********************@per-qv1-newsreader-01.iinet.net.au...

>>Hi Jeff.

I'll give you a qualified "Yes" as the answer to this question.
Yes: A2007 can natively use databases in the 2000 or 2002/3 file format,
but...

a) The user will have to get used to the ribbon instead of menus and
toolbars. If you used custom toolbars, they will appear as an option on
the ribbon, so the interface may not be as you expect. You'll need to
explore this to check that this is okay.

b) There are some bugs in A2007 that mean most of my database don't work
properly. For example, if you use Report_Open to assign the Control
Source of controls in a report (fairly common with crosstabs etc),
attempting to open this report will crash Access 2007. List of things to
check:
http://allenbrowne.com/Access2007.html#Bugs

c) You might want to check this out:
Prevent Access 2007 users modifying existing databases
at:
http://allenbrowne.com/ser-69.html
You can use Access 2003 to run the code. It does stuff like creating the
properties that block layout view, and prevent users from making schema
changes in datasheets (such as renaming or adding fields on the fly.)

"Jeff" <no******@asken.com.auwrote in message
news:46***********************@per-qv1-newsreader-01.iinet.net.au...
This is something I can't test (don't have 2007) and found no
definitive answer, but a few conflicting ones.

Will a 2003 database work correctly in Access 2007?

Don't want to do any design work, just execute and use the database in
2007.

And will Office and Access 2003 work correctly in Vista?

Jeff
"More Access Stuff."
http://www.asken.com.au

[Allen Browne]

IMHO, it needs 1GB of RAM.

If the graphics card is ordinary, be sure not to use Aero (i.e. the basic
Vista would be a good match.) It should be okay.

--
Allen Browne - Microsoft MVP. Perth, Western Australia
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"Jeff" <no******@asken.com.auwrote in message
news:46***********************@per-qv1-newsreader-01.iinet.net.au...

>I am thinking of getting a basic box to install 2003. I looked at a HP
Pavilion (not my fav brand) with just 512mb, 1.66 MHz dual and think it
will be okay. Maybe upgrade to 1 GB mem. But it only comes with Vista hence
the Vista question. At $598 (no monitor) seems a good price.

I will then use a KVM switch to switch between 3 system I have under my
desk.

So only one version on each box. Seems simpler for me and and outlay of
$650 including the switch seems a bargain.

Just not yet convinced the box will run Vista and 2003 well.

"Allen Browne" <Al*********@SeeSig.Invalidwrote in message
news:46***********************@per-qv1-newsreader-01.iinet.net.au...

>Yes: developing in 2003 on Vista is fine.

I suggest you create your own shortcut to msaccesse.exe, and check the
box for:
Run As Administrator
so you don't run into this kind of problem:
Errors using multiple versions of Access under Vista
at:
http://allenbrowne.com/bug-17.html

--
Allen Browne - Microsoft MVP. Perth, Western Australia
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"Jeff" <no******@asken.com.auwrote in message
news:46***********************@per-qv1-newsreader-01.iinet.net.au...

>>Hi Allen

I don't have any custom menus or toolbars, generally, so only a problem
with select databases.

'b' may be an issue. I will have to check the code. Been a while since I
wrote it.

The databases are usually delivered as MDEs and users understand they
are not to modify anything that can be modified (I say jokingly). Are
earlier version MDEs a problem at all in 2007.

What about developing in 2003 in Vista? I think I remember you saying
before that this is okay.
"Allen Browne" <Al*********@SeeSig.Invalidwrote in message
news:46***********************@per-qv1-newsreader-01.iinet.net.au...
Hi Jeff.

I'll give you a qualified "Yes" as the answer to this question.
Yes: A2007 can natively use databases in the 2000 or 2002/3 file
format, but...

a) The user will have to get used to the ribbon instead of menus and
toolbars. If you used custom toolbars, they will appear as an option on
the ribbon, so the interface may not be as you expect. You'll need to
explore this to check that this is okay.

b) There are some bugs in A2007 that mean most of my database don't
work properly. For example, if you use Report_Open to assign the
Control Source of controls in a report (fairly common with crosstabs
etc), attempting to open this report will crash Access 2007. List of
things to check:
http://allenbrowne.com/Access2007.html#Bugs

c) You might want to check this out:
Prevent Access 2007 users modifying existing databases
at:
http://allenbrowne.com/ser-69.html
You can use Access 2003 to run the code. It does stuff like creating
the properties that block layout view, and prevent users from making
schema changes in datasheets (such as renaming or adding fields on the
fly.)

"Jeff" <no******@asken.com.auwrote in message
news:46***********************@per-qv1-newsreader-01.iinet.net.au...
This is something I can't test (don't have 2007) and found no
definitive answer, but a few conflicting ones.
>
Will a 2003 database work correctly in Access 2007?
>
Don't want to do any design work, just execute and use the database in
2007.
>
And will Office and Access 2003 work correctly in Vista?
>
Jeff
"More Access Stuff."
http://www.asken.com.au

[Jeff]

Thanks for that. I agree with the 1GB. Just not sure aboput HP after a
disappointing experience some years ago. But hard to beat the price.

"Allen Browne" <Al*********@SeeSig.Invalidwrote in message
news:46***********************@per-qv1-newsreader-01.iinet.net.au...

IMHO, it needs 1GB of RAM.

If the graphics card is ordinary, be sure not to use Aero (i.e. the basic
Vista would be a good match.) It should be okay.

--
Allen Browne - Microsoft MVP. Perth, Western Australia
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"Jeff" <no******@asken.com.auwrote in message
news:46***********************@per-qv1-newsreader-01.iinet.net.au...

>>I am thinking of getting a basic box to install 2003. I looked at a HP
Pavilion (not my fav brand) with just 512mb, 1.66 MHz dual and think it
will be okay. Maybe upgrade to 1 GB mem. But it only comes with Vista
hence the Vista question. At $598 (no monitor) seems a good price.

I will then use a KVM switch to switch between 3 system I have under my
desk.

So only one version on each box. Seems simpler for me and and outlay of
$650 including the switch seems a bargain.

Just not yet convinced the box will run Vista and 2003 well.

"Allen Browne" <Al*********@SeeSig.Invalidwrote in message
news:46***********************@per-qv1-newsreader-01.iinet.net.au...

>>Yes: developing in 2003 on Vista is fine.

I suggest you create your own shortcut to msaccesse.exe, and check the
box for:
Run As Administrator
so you don't run into this kind of problem:
Errors using multiple versions of Access under Vista
at:
http://allenbrowne.com/bug-17.html

--
Allen Browne - Microsoft MVP. Perth, Western Australia
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"Jeff" <no******@asken.com.auwrote in message
news:46***********************@per-qv1-newsreader-01.iinet.net.au...
Hi Allen

I don't have any custom menus or toolbars, generally, so only a problem
with select databases.

'b' may be an issue. I will have to check the code. Been a while since
I wrote it.

The databases are usually delivered as MDEs and users understand they
are not to modify anything that can be modified (I say jokingly). Are
earlier version MDEs a problem at all in 2007.

What about developing in 2003 in Vista? I think I remember you saying
before that this is okay.
"Allen Browne" <Al*********@SeeSig.Invalidwrote in message
news:46***********************@per-qv1-newsreader-01.iinet.net.au...
Hi Jeff.
>
I'll give you a qualified "Yes" as the answer to this question.
Yes: A2007 can natively use databases in the 2000 or 2002/3 file
format, but...
>
a) The user will have to get used to the ribbon instead of menus and
toolbars. If you used custom toolbars, they will appear as an option
on the ribbon, so the interface may not be as you expect. You'll need
to explore this to check that this is okay.
>
b) There are some bugs in A2007 that mean most of my database don't
work properly. For example, if you use Report_Open to assign the
Control Source of controls in a report (fairly common with crosstabs
etc), attempting to open this report will crash Access 2007. List of
things to check:
http://allenbrowne.com/Access2007.html#Bugs
>
c) You might want to check this out:
Prevent Access 2007 users modifying existing databases
at:
http://allenbrowne.com/ser-69.html
You can use Access 2003 to run the code. It does stuff like creating
the properties that block layout view, and prevent users from making
schema changes in datasheets (such as renaming or adding fields on the
fly.)
>
"Jeff" <no******@asken.com.auwrote in message
news:46***********************@per-qv1-newsreader-01.iinet.net.au...
>This is something I can't test (don't have 2007) and found no
>definitive answer, but a few conflicting ones.
>>
>Will a 2003 database work correctly in Access 2007?
>>
>Don't want to do any design work, just execute and use the database
>in 2007.
>>
>And will Office and Access 2003 work correctly in Vista?
>>
>Jeff
>"More Access Stuff."
>http://www.asken.com.au