access 2003 and win xp

[ever]

I have microsoft access 2003 and Windows xp. I have install access. When I
try to use the wizard in the program I get the fallowing message
Microsoft office access can't start the wizard or add-in. When Ipush OK it
comes back with. Microsoft office access could'nt launch the lookup wizard,
or this wizard has been disable. Can someone tell me How to fix this. I have
reinstall the program a few time but with no luck.

 

[Tim Ferguson]

Microsoft office access couldn't launch the lookup wizard,

Count yourself lucky. The Access Lookup field wizard misfeature has caused
more unhappiness than almost anything since the Black Death.

It takes very little time just to create the tables you want and the
appropriate relationships, and then use a proper combo or list box on your
forms. And the benefits you reap include the whole thing working as _you_
intend, rather than you having to guess what is actually being stored
where.

Hope that helps

Tim F

 

[ever]

Doing it myself is good if you know how. I am trying to do a list of name
that would scrol down and I would be able to choose from the list. I dont
seem to be able to do it

 

[Tim Ferguson]

Doing it myself is good if you know how. I am trying to do a list of
name that would scrol down and I would be able to choose from the
list. I dont seem to be able to do it

No big deal: this is basic R design

Create a table of whatever-the-names-belong-to: let's guess these are
people. You could have something that looks like

People (*PersonID, FName, LName, Department, DateOfBirth)

or whatever else you need to know about them. The * means that the
PersonID is the primary key: an autonumber is as good as anything else if
they don't have some kind of dependable identifier already.

Now, in the other table that needs to be linked to the people (let's call
it Sales), you need a field that points to the PK of the People table.
Something like

Sales (*InvoiceNumber, DateAgreed, Salesman, Amount, etc)

The Salesman field should be a Long Integer (because it has to match the
Autonumber in the People table. If you used some other PK type, then the
data types have to match exactly). By the way, a quirk of Access is that
it sets the Default Value of numeric fields to zero, which you absolutely
don't want, so just rub it out or set it to "NULL".

Finally, you want the db engine to police the values in Sales.Salesman so
that they can never, ever, point to a non-existent Person. Open the
relationships window, add the two tables, and drag Sales.Salesman over
the People.PersonID and then check the "Enforce Relational Integrity"
box. Until you know what you are doing, leave the two Cascade boxes
empty.

That's all there is to it. When you make your form, you can either use
the Control Wizard or put your own settings in a combo box. You want two
columns in the RowSource: one invisible one to hold the People.PersonID
and one visible one to show the names People.LName & ", " & People.FName.

Easy peasy. In many people's opinion (mine included) easier and _far_
safer than that mean old Look Up Wizard. Once you have done this a couple
of times, it takes about five mouse clicks and no thought whatsoever.

If any of that does not make sense, do post back!
With best wishes


Tim F