A2K app doesnt work on all A2k Machines

[Bain]

[RESOLVED] A2K app doesnt work on all A2k Machines

I have written a number of small Access 2000 apps recently. I have run into a problem with other Access 2000 machines not being able to fully run these apps.

Example 1:
I have a report which uses the MonthName() function. It runs fine on my PC, and some other Access 2000 PC's. However others it give me and error saying it doesnt recognize the MonthName() function.

Example 2:
I have yet another report in a different app than the one mentioned above. It runs fine on my PC, and my boss's also. When co-worker tried to run a couple of the reports (all unbound contols filled by VBA code) It says that the report opening was canceled.



Would this be caused by different installation types (typical, full, express...etc) of Access? Any other suggestions?

 

[The_Doc_Man]

Your problems fall in one or two categories.

Problem 1: Unknown function - this is clearly missing reference.

Background: References are made by MS Access but kept in the registry, which is machine-specific. You must visit the failing machines, open the .MDB file to any module showing any code (even a new module, for this purpose). Follow menu-bar path Tools >> References. In the resulting dialog box, some items might be prefixed by (all caps) MISSING:

Select the missing reference so it is highlighted. One of the things you will see at the bottom of the dialog box is the fully qualified file spec of the file that Access wanted to see - but didn't. Make a note of this file name and then UNCHECK the box. Using the Browse option on that box, or using the Start >> Search >> Files and Folders option, locate the file of that name anywhere on the computer in question. Having located the file, you can now use the Browse button from the dialog box to identify it. For each missing file, find the file and check the box.

Possible alternative: Just uncheck the boxes and try to recompile all code. Odds are this won't work correctly - but you might get lucky.

Possible further actions: If any of the items are ActiveX, you will have to also re-register the ActiveX items. This is menu-bar path Tools >> Register ActiveX Controls ... If the file type is .OCX, odds are you will need to do this step, too.

Problem 2: VBA-based actions won't run on some machines.

This could be differences in security settings on the machines that won't run the VBA code or it could be missing references. Try the solution for #1 above first. Bad references CAN cause this - but other things can do this, too. Whereas the first problem is almost ALWAYS reference-related.

If that fix doesn't work, you need some help finding the security settings. You want to see if the balky machines have been set up to refuse to run embedded code. (Which VBA is, so don't blame the machine - it was just doing its job...)

In particular, if the App is run from a network-based disk, your network security settings might be set to disable macros. Which in the unfortunate case of Access, really means VBA, 'cause Access assigns another meaning to the term 'macros'.

 

[Bain]

http://www.utteraccess.com/forums/s...ber=546025&page=2&view=collapsed&sb=5&o=&vc=1

I got the kinks worked out.

Both problems seemed to be caused by the MonthName issue. I created a wrapper function like the one described in the link, and everything works fine!