Access2000 Runtime version

Topic

New Reply

I have created an application that allows its users to view and print different reports. I install the application which includes the Access runtime version onto the client computer. The problem is that it works on some of the computers but not all of them. They are all similiar in hardware(mostly IBM pentiums -233 450 MHZ)using Windows95/98/ME. For some unknown reason I get a runtime error on the computers that don’t have office 2000 installed on them, then the application shuts down. It works fine on the computers with Office 2000 installed. There are a lot more details to it but I was wondering if anyone has had a similiar experience and if so how did they overcome it.

Reply | Quote

Replies

Hi there

Can you let me have more detail about the runtime error message. I presume when you created the program that you included the option for runtime at the point of creation otherwise it will not load correctly.

Reply | Quote

Hi Mich thanks for replying.
Over the past few days I have been working on this problem. I have narrowed it down to certain lines of code.(where the code is calling another procedure) Although I’m not sure why the code that I have runs on some computers but not others. As for more detail on the error message I’ve tried to attached a word document with a picture of the screen and the error message but it wouldn’t attach. But the error message reads “Execution of this application has stopped due to a run time error.” “The Application can’t continue and will be shut down”.
I do have error handling but it does not seem to catch this error.
You mentioned to include the “option for runtime at the point of creation”, are you referring to the Include Runtime checkbox in the Package & Deployment Wizard? If so I have included it, otherwise could you further explain what you were referring to.
I am checking to see if the same section of code is causing the runtime error on some of the other computers. Once I have confirmed this would it help if you could see some of the code(VBA).

Thanks
Jon

Reply | Quote

Hi Jon

Have you checked that the procedures you are calling are not just limited to Office 2000?

Has the program worked before in a previous version of Access eg 97.

Sorry I cant be any more help
Mich

Reply | Quote

Hi mich / charlotte
After more testing I have found that anytime I use the Left() or Mid() function I get the runtime error.(but only on computers without office 2000)I developed the application using MS Office Developer 2000 so the runtime version is Access 2000, therefore I can’t test this one in Access 97.
But I have created basically the same application in Access 97 and it works fine, but it is only run on computers that have Access 97 installed. The idea is to replace the Access 97 versions with the new Runtime 2000 versions so I can give more users the ability to access this reports application. Otherwise the company would have to purchase a Access 97 or 2000 licence for each user.But back to my problem, have you had any problems using the Left() or Mid() functions with a runtime version?
Thanks

Jon

Reply | Quote

Jon:
…. it looks like your message is over a month ago, so this post may not help.
…. I ran into a similar problem when developing an Access app on a 95 machine, and then distributing to 98 machines.
…. In our case, it was the comctl32.dll – my version was on the ‘5’ level, and those on ’98 machines had a ‘6’ level version, and that broke the reference to the library. Hmmm, I just went searching for the KB article #, and I couldn’t seem to pull it up, but there is an article on this problem and a couple of ways to fix it (manual and by code).
…. This may not be the reason, I seem to remember seeing a similar problem resolved in a different way, right here in the Access section of Woody’s Lounge, but you might want to look at this!
… thx
… Pat

Reply | Quote

Is your runtime version using commandbars that call things like Print? If so, you’ll get errors, since the built-in functions like Print are not available in runtime. You have to build and reference your own code to cover them. There are certain libraries that are not redistributable, so the functions that live in those libraries are only available on machines with Access installed. However, you can still write code will work. For example, this is my commandbar code for printing the current page of a report:

Public Function cbPrintPage()
‘Created by Charlotte Foust 4/5/2000
Dim rptCurr As Report
Set rptCurr = Screen.ActiveReport
With rptCurr
DoCmd.SelectObject acReport, rptCurr.Name
DoCmd.PrintOut acPages, .Page, .Page
End With
Set rptCurr = Nothing
End Function

Reply | Quote