Assuming you mean FileSystemObject, did you set a reference to scrrun.dll?

To avoid needing to set the reference, you can use late binding.

Rather than:

Dim mclsFO As FileSystemObject

  Set mclsFO = New FileSystemObject

use

Dim mclsFO As Object

  Set mclsFO = CreateObject("Scripting.FileSystemObject")

It means that the library that carries the definition for FileObject is not
available in Access 2003.  What library were you using in Access 2000 for
this class?  It's not in the default libraries, or even the most common
libraries that aren't the defaults.  (There's a FileSystemObject class in the
Scripting library (scrrun.dll), but that's not the same thing).

You may need to re-register this Active-X control.  Look in the References
and see whether there are any libraries marked "MISSING:" and if so, look at
the path and file name.  Use this path to re-register the library in the
Windows Start -> Run dialog window.  For example, if it were the DAO library
that needed to be re-registered, it would be:

Regsvr32.EXE "C:\Program Files\Common Files\Microsoft Shared\DAO\DAO360.DLL"

You say you were "upgraded from Access 2000 to 2003."  Was that just a
removal of Access 2000 and an installation of 2003, or was that a new image
on your computer?  If it's the latter, then the library defining FileObject
may not even be on your current computer any more.

HTH.
Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips.

(Please remove ZERO_SPAM from my reply E-mail address so that a message will
be forwarded to me.)
- - -
If my answer has helped you, please sign in and answer yes to the question
"Did this post answer your question?" at the bottom of the message, which
adds your question and the answers to the database of answers.  Remember that
questions answered the quickest are often from those who have a history of
rewarding the contributors who have taken the time to answer questions
correctly.