Re: Developing in Access 2003 for Access 97 users
- From: "Allen Browne" <AllenBrowne@xxxxxxxxxxxxxx>
- Date: Wed, 21 Dec 2005 11:07:06 +0800
Dean, if you have Access 97 as well as 2003, I would agree with Lyle that it
would be better to use 97 to develop this database. I actually did a small
one earlier this year using 2003 and converting back at the end: if I had
that time again, I would do the whole thing in A97.
It kinda depends what functionality you use, but avoid stuff like:
- Conditional Formatting
- the Undo event of the form.
- OpenArgs for OpenReport.
- VBA functions such as Replace() and Split().
- ADO-specific code (especially DDL)
If you do convert back, decompile first. Avoid any references other than
VBA, Access and DAO. After conversion to A97, you will still need to change
your DAO reference to 3.51. (A2003 doesn't make that change for you.)
--
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.
"Lyle Fairfield" <lylefairfield@xxxxxxx> wrote in message
news:1135123457.218336.16840@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> DeanL wrote:
>> I know you can convert a database from Access 2003 to 97 easily but is
>> there anything that I should avoid doing in Access 2003 that might make
>> my database incompatible with Access 97?
>
> Starting.
.
- Follow-Ups:
- Re: Developing in Access 2003 for Access 97 users
- From: David W. Fenton
- Re: Developing in Access 2003 for Access 97 users
- References:
- Developing in Access 2003 for Access 97 users
- From: DeanL
- Re: Developing in Access 2003 for Access 97 users
- From: Lyle Fairfield
- Developing in Access 2003 for Access 97 users
- Prev by Date: Re: Contingent formatting
- Next by Date: Re: An aid to inserting a Date, Small calender pops up
- Previous by thread: Re: Developing in Access 2003 for Access 97 users
- Next by thread: Re: Developing in Access 2003 for Access 97 users
- Index(es):
Relevant Pages
|