Run Timing Applications

[Paula_NZ]

I am looking for someone on a paid basis to runtime an application for me. The application has been created in Access 2000. I also need to ask a few questions of someone knowledgable in this field.

 

[mark curtis]

What do you need to know?

 

[Paula_NZ]

Mark, thankyou for your response. I am unfamiliar with 2003 Run Time. Can you fairly simply run time an application or are there alot of modifications / further programming required, bearing in mind I use a fair few macros. Can a run time programme be accessed in design view to make mods or does the original need to be modified and then re runtimed. Are you personnally able to run time and application for me and if so what dollar range are we in. If required I can send you a sample application.

 

[Paula_NZ]

Another thing Mark. What is the Microsoft stance on distribution of run time applications and liscensing

 

[mark curtis]

Can you fairly simply run time an application or are there alot of modifications / further programming required, bearing in mind I use a fair few macros. The only real problems with compiling a runtime are if you are to use sms to distribute it and/or if you have any activeX controls that need to be distributed with it and you forget to include them.

Can a run time programme be accessed in design view to make mods or does the original need to be modified and then re runtimed. You will have to create another runtime and redistribute.

Are you personnally able to run time and application for me and if so what dollar range are we in. If required I can send you a sample application. I could runtime the app for you but would need to know more therefore email me mark_curtis_69@yahoo.com

Thanks
Mark

 

[Rich]

You'll have to ditch your macros and convert them to vba with error handling, else in a run time your db will crash

 

[Pat Hartman]

Paula, I don't think you understand what the Access runtime is. There are lots of posts here on the topic. You can easily find them by searching. The package and deployment wizard which actually creates the "runtime package" doesn't change your db at all. It simply gathers together all the necessary user files along with the MSAccess.exe runtime version and creates a bunch of .cab files and an .exe to extract your files from the .cab files and install them on the target machine.

Here's a little more detail:
What IS the runtime?