T
Ted Dutter
Hi,
I encountered a weird problem today that I am hoping
someone could shed some light on.
My client uses a program that is an Access run-time
database. He has Windows XP and Office XP (including
Access 2002). He has the latest patches as of 9/19/2003
for both. I can tell the run-time database was not
created with Access 2002 because when I open it Access,
it wants to convert it.
There is a field in the database that is numeric.
However, when you try to type a number in the field, it
will only accept 1 digit. Any numbers typed after that
digit do not get entered into the field or displayed on
the screen. The cursor just blinks after the 1st digit
as if you had stopped typing.
However, if I type a number greater that 1 digit in
notepad. Then, copy and paste it into the field, the
number is accepted. This field is used in calculations,
so I can tell that it accepted the number correctly.
The company that produces the software is shrugging their
shoulders (they have seen it 4 times before, but have no
solution and say it is not their problem).
In summary: typing bad, pasting good.
Weird but true. Any suggestions?
Thanks,
Ted Dutter
I encountered a weird problem today that I am hoping
someone could shed some light on.
My client uses a program that is an Access run-time
database. He has Windows XP and Office XP (including
Access 2002). He has the latest patches as of 9/19/2003
for both. I can tell the run-time database was not
created with Access 2002 because when I open it Access,
it wants to convert it.
There is a field in the database that is numeric.
However, when you try to type a number in the field, it
will only accept 1 digit. Any numbers typed after that
digit do not get entered into the field or displayed on
the screen. The cursor just blinks after the 1st digit
as if you had stopped typing.
However, if I type a number greater that 1 digit in
notepad. Then, copy and paste it into the field, the
number is accepted. This field is used in calculations,
so I can tell that it accepted the number correctly.
The company that produces the software is shrugging their
shoulders (they have seen it 4 times before, but have no
solution and say it is not their problem).
In summary: typing bad, pasting good.
Weird but true. Any suggestions?
Thanks,
Ted Dutter