Macro Problem

Hi Please help. I have a database which requires a message to come up
when certain part numbers are added to it. I have solved part of this
by using a conditional macro eg [part no]= 54125 and using a msg
box. This works fine until a part no. which contains a letter is used
eg B6541. Access changes the criteria in the condition box to Part
No]=[b6541] and won't let me take the parameter boxes out. If I leave
them in I get an error message "type mismatch" Does anyone know a way
round this?
Regards

Net wrote:>
It's a text field so put quotes around the value.
>
[part no]= "54125"
[part no]= "b6541"
>
--
Rick Brandt, Microsoft Access MVP
Email (as appropriate) to...
RBrandt at Hunter dot com

Many thanks for that, just tried it - the parameters no longer get
applied but I'm still getting the "type mismatch" warning coming up.
Any ideas where I'm going wrong?
Thanks

Net wrote:Hi Rick,>
Sorry, I'm not very familiar with macros. Where exactly is a type mismatch
error occurring?
>
--
Rick Brandt, Microsoft Access MVP
Email (as appropriate) to...
RBrandt at Hunter dot com

On Apr 2, 10:42 pm, "Rick Brandt" <rickbran...@hotmail.comwrote:
>>>>
Hi Rick,
I'm using a form to update the database and I've got the macro set up
to operate after update in the form (the macro is set on my part
number entry). After entering the part number (with a letter in it)
The "type mismatch comes up. It is working a treat when I only have
numbers to put in and it is displaying the correct error message when
a problem part number is entered but it doesn't like me entering
letters in. It's driving me mad!
Regards

On 2 Apr., 23:50, "Net" <n...@fsmail.netwrote:
>
>
>
>
>>>>>>
Often this happen for example if you enter letters into a numeric
field.
Maybe the field in the table is marked as "numeric".
Try and mark it as "text".
>
Marco P- Hide quoted text -
>
- Show quoted text -

Thanks but the field is marked as "text". I think I'm going to have to
learn a bit of programming!

On 3 Apr., 20:37, "Net" <n...@fsmail.netwrote:
>>
It would be generally very useful if you could write subs and
functions but for this specific problem I don't think it would help,
as most "type mismatch" come from some type mismatch.
>
So I did this: I put a field named PartNo of type 'text' in some
table, then I put on some form a control named PartNo and bound it to
the field PartNo in the table.
Then I made a macro 'test' with the condition: [PartNo]="123456" and
the action: MessageBox "wrong", and set this macro in the event
AfterUpdate of the form.
>
When I enter 654321 in the form nothing happens, when I enter 123456 I
get a MsgBox "wrong".
>
Then I changed the condition of 'test' from [PartNo]="123456" to
[PartNo]="X23456"
>
When I enter 654321 in the form nothing happens, whem I enter X23456 I
get a MsgBox "wrong".
>
The I went to editing the table and changed the data type of field
PartNo from text to number and saved.
>
After that when I enter 654321 in the form nothing happens, whem I
enter X23456 I get a message that the value I entered is not allowed
for this field. In my opinion this proves that the type mismatch comes
when saving the field and before the macro is called.
>
I think you should get the error even if you delete the macro from the
event AfterUpdate and I cannot imagine any other cause to the problem,
than the field PartNo being of type number. Maybe you look in the
wrong table.
>
I don't think you can work around this with some programming, but you
can try: Go to modules and make a new one, then write in it
>
sub test(ByVal A as variant)
if A="X23456" then MsgBox "wrong"
if A="Y65432" then MsgBox "wrong"
....
end sub
>
and save, then go to the form and write in procedure
PartNo_AfterUpdate():
>
call test([PartNo])
>
And let me know if you find a different cause at last, I'm very
interested in learning something new.
>
Greetings
Marco P