I have a file in which the code was done in Excel 2003. Modifications were
made on a machine which has Excel 2000 and now the file will only run on
Excel 2000 and will not run on Excel 2003. I get the error message when
opening:

Cannot exit design mode as cmdShowForm cannot be created

Can anyone help me with this error please?

Hi
What controls are on the form?

regards
Paul

Hi Paul,

There are a number of controls on the form, including Textboxes, Option
buttons and Checkboxes

" wrote:

Hi
What controls are on the form?

regards
Paul

Hi
Thought it might be a slightly different fancy control, like a
calendar, causing the glitch. What is the security setting on the file
- putting it on high can dump you into design mode sometimes. Try
setting it to medium or low.

regards
Paul

Hi Paul,

Setting is medium. The file runs on Excel 2000, but will not run on Excel
2003 or 2002.

It is stopping at bog standard lines of code such as frmMain.Show etc.

" wrote:

Hi
Thought it might be a slightly different fancy control, like a
calendar, causing the glitch. What is the security setting on the file
- putting it on high can dump you into design mode sometimes. Try
setting it to medium or low.

regards
Paul

Hi
Was the code updated on the other machine using VB or VBA? If VBA, all
controls are "design time" controls (a licensing issue) while in VB
they can be "run time" controls. You may now be trying to access
properties of a VB created "run time" control.
I don't know how you would fix that apart from removing the offending
controls and putting back the VBA ones. You might try installing VB on
your machine - that might fix it. Hardly practical though as a work
around.

regards
Paul

Hi Paul,

The code was updated on the machine running Excel 2000 using VBA. I just
can't understand where the problem is. When there is a problem with one form,
I replaced the form and it ran so far until the next error, so I replaced
that and it ran a bit further, but I get so far and then the error reverts to
the first form again. I have been trying to solve this for 3 days! There are
33 forms, many with over 200 textboxes and other controls on them, so I don't
really want to start again.

" wrote:

Hi
Was the code updated on the other machine using VB or VBA? If VBA, all
controls are "design time" controls (a licensing issue) while in VB
they can be "run time" controls. You may now be trying to access
properties of a VB created "run time" control.
I don't know how you would fix that apart from removing the offending
controls and putting back the VBA ones. You might try installing VB on
your machine - that might fix it. Hardly practical though as a work
around.

regards
Paul