Access Runtime problem 4

[Storyteller]

Hello All,
I have created an Access solution that has been split into BackEnd and FrontEnd databases.

The client uses Access 2000 runtime for the FrontEnd, with one computer with Full Access 2000 to allow for inhouse modifications.

The usual course of events is that I work on the FrontEnd offsite and then copy over the Clients copy with the newest version. This has been working perfectly.

Now however, I have hit a glitch and I'm at a loss. The latest update works great on all computers except two.
Now here is the weird part, they can open properly parts of the new version, however there are a number of forms and controls that when they use them they get the following error message:
- Undefined function "Mid" in Expression -
or the Application will quit due to a runtime error.
The strange thing is that none of the forms/controls have "Mid" in their coding and I have added error handling to all code.

The even stranger thing is that the archived version that all computers can use properly was the starting point for the new version.

I have uninstalled and reinstalled Access 2000 runtime from the MOD 2000 SR-1 disk and nothing has worked.

Any suggestions/comments?

Thanks,
Michael

 

[PHV]

Check the references at this 2 computers.
Have all the computers the same MDAC version ?

Hope This Helps, PH.
Want to get great answers to your Tek-Tips questions? Have a look at FAQ219-2884 or FAQ222-2244

 

[Storyteller]

Hello PHV,
I cannot believe how quickly you respond to posts !!!!

The two computers in question are using: MDAC 2.7 SP1 on WinXP SP1. A computer that is working properly is also using the exact same MDAC version on WinXP.

So, that can be checked off the list.

I am going to install the mini version of Access runtime instead of the full version to see if that makes any difference.

Wish me luck.

Michael

 

[jollygood]

Hmm..
I assume you have made sure there are no missing refferences. When you get an error report like this. The missing sub/function name you see is almost allways not the one youre looking for. Access does a check on the whole module when loaded and the error is reporting the first function that is called upon and not nessecary the one causing the trouble.

1.
Make sure you have an error trapp for the Form.OnError.

2.
Do you have youre own modules? Then check there.
Access doesn't load a module untill it is used.

3.
If your app is sometime converted from an earlier version of Access then try creating a blank db and import all stuff into it. This has helped me some times.

4.
Check your queries and format properties.

5.
If theese PCs ever have had Access XP/2002 on them then
you might prepare yourself for a "format c:" operation.
MS Office don't like downgrades.

Hope I've put some light on to it.

 

[Storyteller]

Hello All,
To continue with this tale. . .

I installed the mini version of Access runtime and had the same result. . . nothing.

Jollygood,
I tried suggestion: 3 - creating a new blank copy

After I created the blank database I imported everything into it, including all of the tables. No sense in running BE and FE on a test.

After importing all objects and double checking that they were there I would get the following error message:

The expression On CLick you entered as the event property setting produced the following error:
Error accessing file. Network connection may have been lost.

Now this is really strange as all objects are within the same database.

Any suggestions?

Regards,
Michael

 

[Storyteller]

Hello All,
I did some more research on the error message:
"Error accessing file. Network connection may have been lost."

And there is a solution on the Microsoft website. The suggestions they have are to install Office SP-3 or compile the code.

Being that all computers in question have Office 2000 SP-3, I figured that I would compile the code.

The result is I am no longer getting the "Error accessing file. Network connection may have been lost." error message.

The bad news is that I am back to getting the "Undefined function "Mid" in Expression" error message.

**** slowly pulling my hair out ****

Regards,
Michael

 

[CajunCenturion]

Have you followed through on PHV's first suggestion to check the references on the offending machines against those on a machine that is working?

Good Luck
--------------
To get the most from your Tek-Tips experience, please read FAQ181-2886
As a circle of light increases so does the circumference of darkness around it. - Albert Einstein

 

[Storyteller]

Hello CajunCenturion,
I installed and ran the MDAC Utility Component Checker on the two computers that are having the problems and on one machine that is working correctly. All three machines are using the same MDAC version.

All computers in the Clients office save 1 are using Access runtime. I checked via the full version of Access the references in the Modules and everything appears to be referenced properly.

**** not much hair left ****

Regards,
Michael

 

[CajunCenturion]

This is not about MDAC. It's about program references. Open up the app in the IDE on one of the offending machines, then click Tools->References and see if anything is missing.

Good Luck
--------------
To get the most from your Tek-Tips experience, please read FAQ181-2886
As a circle of light increases so does the circumference of darkness around it. - Albert Einstein

 

[Storyteller]

Hello CajunCenturion,
The two computers in question are using Access 2000 Runtime. Now my understanding is that a User is unable to get to the Database Window or to the Modules when using Access Runtime. This is why there is one full copy of Access in the clients office.

Using the full version of Access I have checked the references and they are all there. Also, the Access Runtime Users are using a shortcut to the same FrontEnd.

What is really confusing is that there are 6 other Users who use the exact same Access Runtime and are all using the latest upgrade with no problems.

Even stranger is that the June 23rd version of the database works great for the two computers that are having the problems with the current version. I have those Users using that version (June 23rd)until I can get this figured out.

*** hoping that hair grows back ***

Regards,
Michael

 

[missinglinq]

I have to say it definitely sounds like a missing reference problem. The "MID" function is an old Basic function actually pre-dating VB 1.o! You may not have the function in your code anywhere, but rather may have a function in your code that in turn uses "MID". Which could be a real bear to find! Don't know much about Runtime, but have you tried re-doing the runtime version?

The Missinglinq

"It's got to be the going,
not the getting there that's good!"
-Harry Chapin

 

[CajunCenturion]

What is most likely happening is that the runtime is trying to find the definition of the Mid function, and being hunting through the included references and stops as soon as it find a reference that it cannot search.

On the development machine, pull up the references dialog box and write down all of the pathnames to the actual file which resolves the reference. Then on the offending machine, search for those files, and see if any are missing.

Good Luck
--------------
To get the most from your Tek-Tips experience, please read FAQ181-2886
As a circle of light increases so does the circumference of darkness around it. - Albert Einstein

 

[Storyteller]

Hello All,
Thanks to everyone who has helped me with this problem. (A star for each of you)

I went back and doubled checked which references were checked in the June 23rd version vs the June 24th version and the only difference is the June 24th version included a reference to Microsoft Office Web Components.

That evening I moved the database to my Home Office and finished the updates and removed the reference to MOWC and today I installed the changes and ALL computers at the Clients office are working correctly.

I'm still not sure why this happened. I am just happy that with the great help from everyone here everything appears to be working great.

Once again thanks to everyone.

Michael