Access 2002 on XP-Home edition

[Bridget McWatters]

I have Access 2002 installed on Microsoft XP-Home edition. But are they
compatible? I am finding that when I try to run an event procedure created
for a form field, it always jumps to a procedure of code that is different
from the event procedure that I am trying to run, and naturally causes a
compilation error because it is the wrong procedure. Then when closing the
VB debugging window, the correct event procedure was found to be behind it,
with the yellow arrow pointing to its title. Since the title is part of the
template generated when programming the event procedure, I cannot see what
programming problem has caused this, and it occurs to me this has something
to do with the installation. Am I correct?

The method used to program this is as follows:-

1) Bring up a form and into design view
2) Select the field to be edited, right click, field properties, event tab
3) Press ellipsis on the OnExit event to go into VB code editor
4) The procedure title and end are generated as template code
5) Entered 1 line of VB code, to set this.fieldname to a variable value
6) Saved it

Attempted to run by filling in the form and tabbing past the field, so that
on exit, it goes into my program code. That is when it gives compile error
as described.
Any suggestions are appreciated. Thank you.

Also, if it is that I should use XP Professional edition, will it work on
laptop, or does it require a new PC?

 

[NetworkTrade]

Access runs on XP home edition. This shouldn't be the fundamental problem.

If you haven't done so - however I would do all the normal updates of the XP
available off the microsoft web site just to be sure it is as up-to-date as
possible though I doubt that will change things - but it is a starting
place...

and XP Professional Edition will not differ between a laptop vs a desktop
version.

As a sanity check I would delete the box from the form. Then re-add a new
box with a new name. And with this new box - do NOT use the ellipses entry
into the VB code on the 'AfterExit' event - but instead create a very simple
macro of some sort and instead reference the macro for that AfterExit event
property.

something simple - like Open Form....

then you should see whether or not the access code is running ok.....this is
quite basic and should be able to be made to run ok...

once your sanity is restored then you can begin experimenting with code in
VB as an alternative....

 

[Bridget McWatters]

Thank you very much, this was very helpful. I did as you suggested and then
discovered it was erroring on the second of 2 duplicate procedures in the
same form module, even though not in the form module for which I was
programming. The code was written by a novice programmer, before handing the
project for me to continue. Having removed the duplicates in all his form
modules and ensuring all procedures have unique names, the problem has now
resolved itself. Thank you very much.
Yours,
Bridget McWatters.