problems with OpenForm - XP

[rightcoast]

Hi,

Hoping someone out there can help with a very frustrating problem...

Have a database created in A2k, works fine on my machine (Windows 2k),
however when running it (an MDE file) on an XP machine, it produces an
error on the following line:

DoCmd.OpenForm strFrm, , , , , , strOA

'strFrm' and 'strOA' are passed to the procedure as
'frmCreateProposal' and 'PE'. The error says it cannot find form name
'PE', which is actually the opening argument, not the form name. For
some bizarre reason, it seems to be interpreting the opening argument
as the form name, but only on the XP machine. Is this potentially a
Windows 2k/XP problem, or an MDE problem??

Any insights/suggestions/solutions will be most welcome.

Thanks.

[Allen Browne]

At a guess, this is more likely to be a difference in service packs than in
operating system.

Do both machines have SP3 for Office XP installed? There is a (somewhat
different) reference to OpenArgs being addressed in SP3 in this article:
http://support.microsoft.com/?id=836030

--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"rightcoast" <ri***********@yahoo.com> wrote in message
news:6d**************************@posting.google.c om...

Hoping someone out there can help with a very frustrating problem...

Have a database created in A2k, works fine on my machine (Windows 2k),
however when running it (an MDE file) on an XP machine, it produces an
error on the following line:

DoCmd.OpenForm strFrm, , , , , , strOA

'strFrm' and 'strOA' are passed to the procedure as
'frmCreateProposal' and 'PE'. The error says it cannot find form name
'PE', which is actually the opening argument, not the form name. For
some bizarre reason, it seems to be interpreting the opening argument
as the form name, but only on the XP machine. Is this potentially a
Windows 2k/XP problem, or an MDE problem??

Any insights/suggestions/solutions will be most welcome.

Thanks.

[rightcoast]

Thanks for the reply. Not sure about the service packs but - as often
happens, I resolved my own issue shortly after posting the message.

When I ran the mdb on the XP machine, it worked fine, so I guessed
that the problem was the mde. So...I converted the mdb to Access 2002
format, then created the mde from that version, and it worked fine. I
haven't the faintest clue why the A2k mdb would function correctly on
the XP machine, while the mde created from that same file would not,
but figuring out a way past the problem (and a very simple one at
that...) will have to suffice.
"Allen Browne" <Al*********@SeeSig.Invalid> wrote in message news:<40***********************@freenews.iinet.net .au>...

At a guess, this is more likely to be a difference in service packs than in
operating system.

Do both machines have SP3 for Office XP installed? There is a (somewhat
different) reference to OpenArgs being addressed in SP3 in this article:
http://support.microsoft.com/?id=836030

--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"rightcoast" <ri***********@yahoo.com> wrote in message
news:6d**************************@posting.google.c om...

Hoping someone out there can help with a very frustrating problem...

Have a database created in A2k, works fine on my machine (Windows 2k),
however when running it (an MDE file) on an XP machine, it produces an
error on the following line:

DoCmd.OpenForm strFrm, , , , , , strOA

'strFrm' and 'strOA' are passed to the procedure as
'frmCreateProposal' and 'PE'. The error says it cannot find form name
'PE', which is actually the opening argument, not the form name. For
some bizarre reason, it seems to be interpreting the opening argument
as the form name, but only on the XP machine. Is this potentially a
Windows 2k/XP problem, or an MDE problem??

Any insights/suggestions/solutions will be most welcome.

Thanks.