Re: Run-time error 2465 after database import

Hi Maurice,

I'm not switching versions. The original database is in Access 2000 and the
new one is also Access 2000. Everything is also being done on the same
machine. I'm just trying to create a tidied-up copy of the original
database.

So far the only error I'm encountering is with the function, but I've really
tested very little. I got that error on the first thing I tried after
import, and so I haven't looked any further for other errors.

Thanks!

James




"Maurice" <Maurice@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:9756A92A-E973-4666-B10F-96167626E441@xxxxxxxxxxxxxxxx
James,

What version as you importing into to? What's the old version it comes
from?
Is the function the only problem you are encountering or are you getting
other issues as wel.

--
Maurice Ausum


"James Martin" wrote:

I'm trying to tidy up a database by starting with a fresh, blank database
(Access 2000) and importing everything from the original database. Here
are
the steps I've gone through:

1. Started with a blank database.

2. Set all the properties to be the same as the original database. I've
set
the properties in:
- File / Database Properties
- Tools / Startup
- Tools / Options
- Visual Basic Editor - Tools / database Properties
- Visual Basic Editor - Tools / Options
- Visual Basic Editor - Tools / References

3. Selected File / Get External Data / Import and imported all tables,
queries, etc. (including checking the boxes to import relationships and
menus & toolbars).

After doing all of this I start getting odd errors in the new database
that
didn't exist in the original database. Specifically I'm getting "Run-time
error 2465 ... database can't find the field 'PaddedLotNumber' referred
to
in your expression". PaddedLotNumber is a function I have in one of my
modules. If I go into debug at this point and try using PaddedLotNumber
in
immediate mode, I get the same error. But as soon as I click Stop to end
processing and try using PaddedLotNumber, it works fine.

Initially I assumed that this was being caused by missing or incorrect
references, but I've checked all of them and they are identical in the
two
databases. I can't find any differences between the two databases.
(Except,
of course, that the system tables in the fresh one are lots smaller -
which
is why I'm going through this procedure in the first place.)

I've tried decompiling, compact & repair, recompiling, etc. but I
continue
to get the 2465 error in the new database.

Does anyone have any suggestions as to what might be the problem?

Thanks in advance!

James





.

Relevant Pages

  • Re: The amazing disappearing VBA code
    ... Windows Explorer, and make a copy of your database, as Access is about to ... the original database wasn't deleted because it is read-only. ... might be an issue with mapped drives like when were the last updates from MS ... resource management in the OS or any other application is hoarding RAM. ...
    (microsoft.public.access.modulesdaovba)
  • Re: copying ? Record #isnt working
    ... If you have copied to old database there is no need to put the ... If you wish to keep the old database simply rename it "MyDbOLD.mdb". ... Then re-name the new updated database to the original database name ... ' Rename original Db to a new name in the same folder ...
    (microsoft.public.access.gettingstarted)
  • Re: Altering Identity Columns for Bidirectional Transasctional Replication
    ... Backup the original Database containing all the data: ... Destroy the orginal database and recreate the database only. ... Take the scripts that created the original database (if none is ...
    (microsoft.public.sqlserver.replication)
  • Re: autonummering in table gives problems
    ... manually recreate the "bad" records in the new table, ... sequence of AutoNumber identifications may be regenerated (but don't count ... I made the new database with all the ... > the original database). ...
    (comp.databases.ms-access)
  • Run-time error 2465 after database import
    ... I'm trying to tidy up a database by starting with a fresh, ... Set all the properties to be the same as the original database. ... Visual Basic Editor - Tools / database Properties ...
    (microsoft.public.access.formscoding)