References problem moving MDE database from XP to Vista

[mike sch]

We have an Access 2003 based inventory system custom-designed by someone that is now MIA.

Previously I was running the work-provided desktop computer:

MS Office 2003 + Windows XP

I copied the database files over to my personal laptop, Windows Vista with MS Office 2007 was already installed, and I installed MS Access 2003 to run the Database.

For the most part everything works, but there are a few things that don't, and they are quite key things!

When I go to Tools/References in the VB Editor, it is greyed out. I've tried Resetting the code in case something is running, but it always stays grey.

First:

If I try to print our sales catalogue, it tells me:

doPrint: Function is not available in expressions in query expression 'Format([total_cost].[TotalCost],"Currency")'.

Second:

When I click the button to pull up the lease structure for a vehicle, it tells me:

checkLeaseSourceSetting: Function is not available in expressions in table-level validation expression.

This in itself doesn't seem to prevent me from doing what I need to do... but I don't know if there is something behind-the-scenes that needs to be done that isn't being done because of this error.

Third:

When I try to print the lease documents, it tells me:

Function is not available in expressions in query expression 'LTrim(vehicle_year_1 & ' ' & vehicle_make_1 & ' ' vehicle_model_1)'.

I still have access to the old computer, so if there's any files I can just copy over to my Vista computer to make everything work, that'd be great, because I can't edit anything in the MDE file, obviously.

How would I approach troubleshooting this?

Thanks!!

[Rabbit]

First, there's not much you can do since you can't access the code.

Second, since it's an MDE, the code is compiled and you can't edit the code unless you have the original uncompiled database.

[mike sch]

@Rabbit
Is there a way to view the references when it's greyed out, and then stick the right files in the right place/register libraries to restore whatever is broken?

[mike sch]

@mike sch
Basically what I am concluding is that it's not liking the Trim/LTRim etc statements. I think it's not accessing the MS Office 11 Object Library correctly - possibly accessing a newer object library? How do I correct it and get it back to the Office 11 library?

[Rabbit]

Like I said earlier, you can't change any of the stuff related to code unless you have a copy of the uncompiled database. When a compiled database is created, an uncompiled version should always be kept. If that was not done, there's nothing you can do.

[mike sch]

I'm not talking about changing the actual code - I'm talking about configuring my computer to match the settings of the old computer as closely as possible to avoid the problems in the first place.

MS Access seems to only show the MS Office 14 Object Library as an option, so how do I uninstall that Object Library and try to force everything in Access to use the Office 11 Object Library?

[Rabbit]

Changing references is part of changing the code. Which you can't do because it's compiled.

[mike sch]

But what I'm saying is that, if the references are hard-coded into the MDE, then why can't I shape my computer to match what the code is expecting?

For example, if there is a reference to c:\123.dll but c:\123.dll does not exist on Computer B, then putting 123.dll in c:\ should technically make the reference accurate once again, should it not?

[Rabbit]

Technically yes. But you won't be able to figure out what was referenced in the database without the uncompiled version.