Run-time Version 1

[orna]

Hi

We have about 20 Access applications in the company, and till now we have Access installed on every station. (~200 stations)
Now we need to remove the Access and switch to Run-time.
I know the process but have problem with some Functions.
For instance, the MS Calendar close the application in spite of having an error trapping ,
and there is no mouse right click.
Is there somewhere a list of the functions that can't work in Run-time, and how to workaround it?


TIA

 

[jrbarnett]

When I've been involved in making applications run properly on the runtime, I've needed to do the following:

1. Put a menu system on the application and set it as the startup form as access to the database window is not possible in the runtime. Using the Microsoft Switchboard works fine.

2. Filter by Form doesn't work, so build a proper record selection form that passes a where clause over to forms/reports where needed or dynamically edits the record source. My technique which works well is documented in faq702-3619.

3. Put good error handling in all applications. Anything that falls over needs to display an appropriate error message as the system won't drop into debug mode, and maybe log any useful information into the application for you to look at later.

4. Take out the reference to the Microsoft Office web components as I've had a lot of problems using them with the runtime version, but they've not affected the applications I've developed in the slightest.

5. Either disable the close button on the menu form to stop the user closing it, or set some code up that prompts the user to close the application? Why - without a valid menu system, the user has no way to navigate around the application so needs to close and reopen it.

John

 

[orna]

Thanks John!
Looks very Helpful