Access error message

J

Jonathan

Hello all:
I have an Access2002 database (split back end and front end) running on a
WinXP LAN environment. I have a form in the FE with various bound and
formatted fields. When I enter data into this form from one workstation I'll
get an error message that says: "The value you entered isn't valid for this
field." On clicking the OK button, the cursor advances to the next field on
the form, accepting the item just entered and updating the database. The
data entered in fact complies with format rules. NOW: If I run the same form
with the same input from another workstation I DO NOT get the error message.
I'm running the same version of Access 2002 (SP3) on both machines.

Does any know what might account for this strange behavior? I'm stumped
 
R

RobFMS

Jonathan

The first immediate thing I would determine is if the two PC have different
Access versions. I might speculate that one individual has applied
updates/patches and the other individual has not.

Go to Help - > About Microsoft Access to see the versioning information.

HTH

--
Rob

FMS Professional Solutions Group
http://www.fmsinc.com/consulting

Software Tools for .NET, SQL Server, Visual Basic & Access
http://www.fmsinc.com

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
 
J

Jonathan

The only thing I found was this from the System Info button on
the About box"
=================================
Application name Microsoft Access
Version 10.0
Build 4302
Product ID 54195-640-1866266-16001
Application path C:\Program Files\Microsoft Office\Office10\
Language English (United States)
ADO version Not Available
VBA version 6.04
References Not Available
==================================
This from the workstation with no errors. One of the workstations that that
get the error has a VBA version 6.03 but another has 6.04. Everything else
seems the same.

Any other suggestions?
 
J

Jonathan

I had checked that. All 3 workstations say the same thing:
Microsoft(R) Access 2002 (10.4302.6714) SP3

-Jonathan
 
R

RobFMS

Ok .. now I'm going to start opening my bag of tricks here...

First, let's do a decomiple, compile of both DBs... I want to see if it
shakes it up a bit. What I might expect is that both DBs will give you the
problem after this.

Follow this link to see how to perform the decompile
http://www.fmsinc.com/free/tips.html#accessdecompile

--
Rob

FMS Professional Solutions Group
http://www.fmsinc.com/consulting

Software Tools for .NET, SQL Server, Visual Basic & Access
http://www.fmsinc.com

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
 
J

Jonathan

Okay, I carried out the decompile on both BE and FE dbs. But the error
message remains on 2 PCs but not the other.
No change in behavior.

-J
 
R

RobFMS

Found this during a search. See if this applies:

Error Message: ""The value you entered isn't appropriate for this field."

----------------------------------------------------------------------------
----

may encounter an error that states "The value you entered isn't appropriate
for this field." This may occur when you try to enter a date into a date
field if the date formatting isn't set up correctly in Windows.

The program expects dates to be entered in the format of MM/DD/YYYY or
M/D/YYYY (month/day/year). But Microsoft Windows has a setting that can
cause this to be changed so that even if you follow this format. To make
sure you have your windows setting correct, follow this procedure...

1) Go to the Control Panel (Click on Start then Settings then Control Panel)
2) Click on Regional Settings then click on the Date tab
3) For the short date setting select M/d/yyyy then click on OK


--
Rob

FMS Professional Solutions Group
http://www.fmsinc.com/consulting

Software Tools for .NET, SQL Server, Visual Basic & Access
http://www.fmsinc.com

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
 
J

Jonathan

Rob,
I thought this might have been the problem but it isn't. The regional
setting on both machines are the same. One other thing I see now is that the
form in question is being called up by two different command buttons on the
parent form. On the error machine I get the error message when the form is
called up by one button but not the other. On the other machine, the error
never comes up regardless of the command button used to show it.

I'm at wit's end!
Thanks for your help up to this point. If you have any other suggestions I'd
love to hear them
Best
Jonathan
 
Top