locked
Access 2010 runtime error Mid$() RRS feed

  • Question

  • The mid$ (i.e. msgbox mid$("test",2,1)) command results in a crash on a runtime installation whereas on a full installation using the /runtime function everything is working.

    Systems used: Developing on a Access 2010 32bit installation. Remote system is Windows 7, Access 2010 runtime 32bit (version 14.0.7015.1000).

    Error message: Execution of this application has stopped due to a run-time error. The application can't continue and will be shut down.

    Error handling is active but does not help me any further. It seems like the function is being compiled in the background causing the error before actually running it.

    If this error is caused by a missing reference, how can I check the installed references on the remote system ?

    Thursday, November 6, 2014 7:29 AM

Answers

  • The mid$ (i.e. msgbox mid$("test",2,1)) command results in a crash on a runtime installation whereas on a full installation using the /runtime function everything is working.

    Systems used: Developing on a Access 2010 32bit installation. Remote system is Windows 7, Access 2010 runtime 32bit (version 14.0.7015.1000).

    Error message: Execution of this application has stopped due to a run-time error. The application can't continue and will be shut down.

    Error handling is active but does not help me any further. It seems like the function is being compiled in the background causing the error before actually running it.

    If this error is caused by a missing reference, how can I check the installed references on the remote system ?

    You may check this article written by MVP Doug Steel about references and how to deal with them properly:

    Access References

    Hope this helps,


    Daniel van den Berg | Washington, USA | "Anticipate the difficult by managing the easy"

    Please vote an answer helpful if they helped. Please mark an answer(s) as an answer when your question is being answered.

    • Proposed as answer by danishani Friday, November 7, 2014 5:29 AM
    • Marked as answer by Caillen Monday, November 17, 2014 2:38 AM
    Thursday, November 6, 2014 4:12 PM

All replies

  • The mid$ (i.e. msgbox mid$("test",2,1)) command results in a crash on a runtime installation whereas on a full installation using the /runtime function everything is working.

    Systems used: Developing on a Access 2010 32bit installation. Remote system is Windows 7, Access 2010 runtime 32bit (version 14.0.7015.1000).

    Error message: Execution of this application has stopped due to a run-time error. The application can't continue and will be shut down.

    Error handling is active but does not help me any further. It seems like the function is being compiled in the background causing the error before actually running it.

    If this error is caused by a missing reference, how can I check the installed references on the remote system ?

    You may check this article written by MVP Doug Steel about references and how to deal with them properly:

    Access References

    Hope this helps,


    Daniel van den Berg | Washington, USA | "Anticipate the difficult by managing the easy"

    Please vote an answer helpful if they helped. Please mark an answer(s) as an answer when your question is being answered.

    • Proposed as answer by danishani Friday, November 7, 2014 5:29 AM
    • Marked as answer by Caillen Monday, November 17, 2014 2:38 AM
    Thursday, November 6, 2014 4:12 PM
  • Thanks - problem solved. I was on Google for hours but did not find the article you send me.
    Friday, November 7, 2014 5:12 AM