Form/Subform “value isn't validâ€

  • Thread starter Thread starter yator
  • Start date Start date
Y

yator

(I mistakenly posted this previously on "Queries")

I have a Form with 2 Continuous subforms as follows:

Main Form: frm_doc_con
Record Source: tbl_manual
Fields:
Section: Text
ChapterNo: Text
Chapter: Text
Primary Key: ManNo (AutoNumber-Long Integer) (not shown on form)

SubForm 1: frm_sub_documents
Record Source: tbl_documents
Default View: Continuous
Fields:
DocNo: Text
Title: Text
EffectiveDate: Short Date
Primary Key: D# (AutoNumber-Long Integer) (not shown on form)
FK: ManNo (Long Integer)
Link Child: ManNo
Link Master: ManNo


SubForm 2: frm_sub_rev
Record Source: tbl_rev
Default View: Continuous
Fields:
Revise_Date: Short Date
Review_Date: Short Date
Primary Key: RevNo (AutoNumber-Long Integer) (not shown on form)
FK: D# (Long Integer)
Link Child: D#
Link Master: FrmD#Relay – this is a text box on Main Form Control Source:
=[frm_sub_documents].[Form]![D#]

SubForm 1 works fine for data entry/edit etc. Sub Form 2 gives the following
1. When I try to enter a new record in any date field I get the message “The
value you entered isn't valid for this fieldâ€. After hitting the OK button, I
can proceed to enter data as normal.
2. If I start a new record entry in a Text field I don’t get the error
message. Instead, after typing the first character, the cursor backspaces to
cover that character so that if I keep typing the first character is
overwritten. After this, I can type in any of the new record fields including
dates without any problem.
3. If I have multiple records in SubForm 2, when I go to enter a new record,
the line of the new record jumps to the top so that I can not see the
previous records.

There are no Default Values, Required Fields or any ZeroLength Fields
allowed in any underlying tables. All data types seem to agree. All Text
Boxes have unique names. There are no Modules with any of the forms.
 
Thanks for the response.
I am using Access 97 SR-2.
The only special character or reserved words I had used was the # sign. I
have changed that.
I also have changed all form/subform data sources to queries.
Problem persists.

ruralguy via AccessMonster.com said:
What version of Access are you using? Is it fully patched?

Suggestions:
Always bind forms to queries and not tables.
Do not use special characters in any names other than an the under_score.

Special characters that you must avoid when you work with Access databases
http://support.microsoft.com/?id=826763
List of reserved words in Access 2002 and Access 2003
http://support.microsoft.com/?id=286335
List of Microsoft Jet 4.0 reserved words
http://support.microsoft.com/?id=321266

(I mistakenly posted this previously on "Queries")

I have a Form with 2 Continuous subforms as follows:

Main Form: frm_doc_con
Record Source: tbl_manual
Fields:
Section: Text
ChapterNo: Text
Chapter: Text
Primary Key: ManNo (AutoNumber-Long Integer) (not shown on form)

SubForm 1: frm_sub_documents
Record Source: tbl_documents
Default View: Continuous
Fields:
DocNo: Text
Title: Text
EffectiveDate: Short Date
Primary Key: D# (AutoNumber-Long Integer) (not shown on form)
FK: ManNo (Long Integer)
Link Child: ManNo
Link Master: ManNo

SubForm 2: frm_sub_rev
Record Source: tbl_rev
Default View: Continuous
Fields:
Revise_Date: Short Date
Review_Date: Short Date
Primary Key: RevNo (AutoNumber-Long Integer) (not shown on form)
FK: D# (Long Integer)
Link Child: D#
Link Master: FrmD#Relay – this is a text box on Main Form Control Source:
=[frm_sub_documents].[Form]![D#]

SubForm 1 works fine for data entry/edit etc. Sub Form 2 gives the following
1. When I try to enter a new record in any date field I get the message “The
value you entered isn't valid for this fieldâ€. After hitting the OK button, I
can proceed to enter data as normal.
2. If I start a new record entry in a Text field I don’t get the error
message. Instead, after typing the first character, the cursor backspaces to
cover that character so that if I keep typing the first character is
overwritten. After this, I can type in any of the new record fields including
dates without any problem.
3. If I have multiple records in SubForm 2, when I go to enter a new record,
the line of the new record jumps to the top so that I can not see the
previous records.

There are no Default Values, Required Fields or any ZeroLength Fields
allowed in any underlying tables. All data types seem to agree. All Text
Boxes have unique names. There are no Modules with any of the forms.
Click to expand...

--
RuralGuy (RG for short) aka Allan Bunch MS Access MVP - acXP WinXP Pro
Please post back to this forum so all may benefit.

Message posted via AccessMonster.com
Click to expand...
 
Tried decompile no effect.
Tried importing into new db, and slowly building up the forms from scratch.
It works initially, but it at some point (posisbly when I add one particular
combo box in the 1st subform) I get the weird behavior. I try deleting it,
but at that point it seems like there is no going back. I can't lose the
"value isn't valid" error.

ruralguy via AccessMonster.com said:
The symptoms are weird enough to suspect corruption. Have you tried importing
your db into a new db? How about a /decompile?
http://www.granite.ab.ca/access/decompile.htm
Thanks for the response.
I am using Access 97 SR-2.
The only special character or reserved words I had used was the # sign. I
have changed that.
I also have changed all form/subform data sources to queries.
Problem persists.
What version of Access are you using? Is it fully patched?
Click to expand...
[quoted text clipped - 61 lines]
allowed in any underlying tables. All data types seem to agree. All Text
Boxes have unique names. There are no Modules with any of the forms.
Click to expand...
Click to expand...

--
RuralGuy (RG for short) aka Allan Bunch MS Access MVP - acXP WinXP Pro
Please post back to this forum so all may benefit.

Message posted via AccessMonster.com
Click to expand...
 
New wrinkle. I brought this db home and tried it with Access 97 and Win XP
Pro (we have Win XP at work). The "value isn't valid" prolem disappeared.
Although now I have an even bigger screen flicker problem on my tab control.
I think this may turn out to be an Access 97 - Windows XP problem

ruralguy via AccessMonster.com said:
I don't have ac97 so I can't really try what you have. Maybe someone with
ac97 will drop by and offer assistance. I'm out of ideas, sorry.
Tried decompile no effect.
Tried importing into new db, and slowly building up the forms from scratch.
It works initially, but it at some point (posisbly when I add one particular
combo box in the 1st subform) I get the weird behavior. I try deleting it,
but at that point it seems like there is no going back. I can't lose the
"value isn't valid" error.
The symptoms are weird enough to suspect corruption. Have you tried importing
your db into a new db? How about a /decompile?
Click to expand...
[quoted text clipped - 12 lines]
allowed in any underlying tables. All data types seem to agree. All Text
Boxes have unique names. There are no Modules with any of the forms.
Click to expand...
Click to expand...

--
RuralGuy (RG for short) aka Allan Bunch MS Access MVP - acXP WinXP Pro
Please post back to this forum so all may benefit.

Message posted via AccessMonster.com
Click to expand...
 
Back
Top