I recently finished a system in Access 2003 for a client and loaded it
onto their server. They use the A2003 runtime version. One of the main
forms contains a TAB control. On moving away from one particular page
to any other they received a run time error and the application
closed. This behaviour did not occur when using the full version of
Access.

I managed to solve the problem by deleting and re-creating the
affected page, but nevertheless I was very surprised about this and
now check my work very carefully using the /runtime switch here.

Was I right to be surprised - or is this to be expected ??

Dave

I don't know about the original error, but runtime will shut-down on any
un-handled errors. You need to check that all VBA code has OnError checking.
I don't know but believe A2003 macros don't support error checking, which
will cause Runtime to crash on any macro errors.

"Dave G @ K2" <DaveGriffiths70@gmail.comwrote in message
news:1184084839.836019.59730@w3g2000hsg.googlegrou ps.com...

I recently finished a system in Access 2003 for a client and loaded it
onto their server. They use the A2003 runtime version. One of the main
forms contains a TAB control. On moving away from one particular page
to any other they received a run time error and the application
closed. This behaviour did not occur when using the full version of
Access.
>
I managed to solve the problem by deleting and re-creating the
affected page, but nevertheless I was very surprised about this and
now check my work very carefully using the /runtime switch here.
>
Was I right to be surprised - or is this to be expected ??
>
Dave
>

Well, firstly I never use macros. And secondly I always have error
trapping code in my VBA. But that isn't relevant here because none of
my code runs when moving from one page to another in the tab control.
And don't forget that this problem only occurs when moving away from
one particular page. And also don't forget that no error occurred when
using the full version of Access.

This looks to me like that particular page was corrupted in such a way
that it only showed up when using the runtime version. I didn't
realise this could happen.

So this is a kind of warning - when developing a system that will
eventually be run using the run time version then I strongly recommend
testing it thoroughly in that environment

Dave

It likely was a corruption. It may be a good procedure to repair, compact,
and even recompile before testing and distributing to end users.

"Dave G @ K2" <DaveGriffiths70@gmail.comwrote in message
news:1184089791.809184.179960@g4g2000hsf.googlegro ups.com...

Well, firstly I never use macros. And secondly I always have error
trapping code in my VBA. But that isn't relevant here because none of
my code runs when moving from one page to another in the tab control.
And don't forget that this problem only occurs when moving away from
one particular page. And also don't forget that no error occurred when
using the full version of Access.
>
This looks to me like that particular page was corrupted in such a way
that it only showed up when using the runtime version. I didn't
realise this could happen.
>
So this is a kind of warning - when developing a system that will
eventually be run using the run time version then I strongly recommend
testing it thoroughly in that environment
>
Dave
>