Migration from AC2002 to AC2003?

  • Thread starter Thread starter Henry Smith
  • Start date Start date
H

Henry Smith

I am trying to migrate from Access2000 to Access2003. I am very confused as
to what effort will be involved to migrate my applications from AC2000 to
AC2003. The following snipit of code is from one of my applications. Using
this snipit as an example, what would the AC2003 Visual Studio.net code to
accomplish the same thing look like?

'#######################

Dim db As DAO.Database

Dim Rs As DAO.Recordset

Dim FiscalYear As Long

Dim strSQL As String



Set db = Access.CurrentDb



StrSQL = "Select * From tblPayRecord Where PayYear = " & FiscalYear



Set Rs = db.OpenRecordset(strSQL)

'########################

I have ordered several new books about AC2003, but am trying to get a head
start on my planning while I wait for the books to arrive.

Any assistance or pointers to good web sites in this arena will be greatly
appreciated.



Cheers,

Henry
 
I don't think there is anything you need to do. I've successfully developed
applications in Access 2000 and XP and ran them in 2003 without a problem.
 
Matt,
Thank you for your reassurance. Unfortunately, or fortunately, your
experience seems to go against everything I have read about AC2003 and it
inability to be compatible with AC2000.
How did you resolve your reference problem? How do I make a distributable
application from within AC2000? I do have all the developer's software for
AC2000 and have distributed applications. My last attempt to distribute a
modified AC2000 application failed on install. What am I missing?

Looking forward to your reply.
Cheers,
Henry
 
We are not distributing A2003, but in test, our code
like that shown worked without problem.

(david)
 
David,
Thank you for the feedback.

Will have to some extensive testing as soon as I receive the AC20003
software.

Cheers,
Henry
 
I haven't packaged either with runtime support for distribution, but I run
MDB and ADP in Access 2002 and 2003 _at will_ and have never had the
slightest problem. I sometimes save in Access 2000 format from each of them.
There was very, very little Access-specific change between 2002 and 2003.
Come to think of it, I've never had any problem running an Access 2000 MDB
or ADP in Access 2002/2003, either. That's not to say that there may not be
some things that could be problematical, but my stuff tends to the
bog-standard, normal and it hasn't encountered any.

MDE and ADE are, by definition, not transferrable between versions.

Larry Linson
Microsoft Access MVP
 
Back
Top