Date field in form was working fine, then stopped accepting data

Please help

Did you change the query that your form is based on? What were you doing
just prior to the problem?

I created a query with several calculations in it. I then created an input
form based on that query. The primary key field is work of date. After
spending hours creating the form and reports, I went to enter 2 records in
the form and it worked. When I went to enter the 3rd record in the form it
would not let me type any numbers in the date field. My num-lock is on, all
of the properties are set for data entry, nothing has been changed. It just
stopped working. Has anyone else had this issue and no how to recover from
this problem. I really don't want to start over again. Please
help!!!!!!!!!!!!!!!11

"please help" wrote:

Please help

I inserted a combo box for employee names, just after inserting the combo box
I could not enter any information in the date field on the form. I then
deleted the combo box and it still would not accept any information. I then
went to the query and even in the query I can't type in the date. However,
when I go to the table that this is all based on I can type the date.

"mnature" wrote:

Did you change the query that your form is based on? What were you doing
just prior to the problem?

The primary key field is work of date. After
spending hours creating the form and reports, I went to enter 2 records in
the form and it worked. When I went to enter the 3rd record in the form it
would not let me type any numbers in the date field. My num-lock is on, all
of the properties are set for data entry, nothing has been changed. It just
stopped working. Has anyone else had this issue and no how to recover from
this problem. I really don't want to start over again. Please
help!!!!!!!!!!!!!!!11

The primary key field is work of date? Does that mean you are using a date
as your primary key? A primary key is unique, so once you put a date into
your primary key field, you can not use that date again. Not sure if that is
what is causing your current problem, but it can definitely cause problems in
the future.

One way of checking this is to go back to your query (or table, just this
once), and see if you can enter your data there, rather than in the form.
Check your fields, to see if any other than the primary key are set to unique.

Work of date is my primary key; however, I had 2 primary keys one was work of
date the other was employee name. After having this condition, I went back
to the table and added an auto number as the primary key. Both the form and
the query still will not accept any numbers or data in the date field. When
I type a number it is like my numb-lock is off, but it is not, the numb-lock
is on.

"mnature" wrote:

The primary key field is work of date. After
spending hours creating the form and reports, I went to enter 2 records in
the form and it worked. When I went to enter the 3rd record in the form it
would not let me type any numbers in the date field. My num-lock is on, all
of the properties are set for data entry, nothing has been changed. It just
stopped working. Has anyone else had this issue and no how to recover from
this problem. I really don't want to start over again. Please
help!!!!!!!!!!!!!!!11

The primary key field is work of date? Does that mean you are using a date
as your primary key? A primary key is unique, so once you put a date into
your primary key field, you can not use that date again. Not sure if that is
what is causing your current problem, but it can definitely cause problems in
the future.

One way of checking this is to go back to your query (or table, just this
once), and see if you can enter your data there, rather than in the form.
Check your fields, to see if any other than the primary key are set to unique.

Please post details on the tables you are using in your query. Designate the
primary and foreign keys, especially.

"please help" wrote:

Work of date is my primary key; however, I had 2 primary keys one was work of
date the other was employee name. After having this condition, I went back
to the table and added an auto number as the primary key. Both the form and
the query still will not accept any numbers or data in the date field. When
I type a number it is like my numb-lock is off, but it is not, the numb-lock
is on.

"mnature" wrote:

The primary key field is work of date. After
spending hours creating the form and reports, I went to enter 2 records in
the form and it worked. When I went to enter the 3rd record in the form it
would not let me type any numbers in the date field. My num-lock is on, all
of the properties are set for data entry, nothing has been changed. It just
stopped working. Has anyone else had this issue and no how to recover from
this problem. I really don't want to start over again. Please
help!!!!!!!!!!!!!!!11

The primary key field is work of date? Does that mean you are using a date
as your primary key? A primary key is unique, so once you put a date into
your primary key field, you can not use that date again. Not sure if that is
what is causing your current problem, but it can definitely cause problems in
the future.

One way of checking this is to go back to your query (or table, just this
once), and see if you can enter your data there, rather than in the form.
Check your fields, to see if any other than the primary key are set to unique.

On Thu, 15 Jun 2006 11:06:02 -0700, please help
wrote:

I created a query with several calculations in it. I then created an input
form based on that query. The primary key field is work of date. After
spending hours creating the form and reports, I went to enter 2 records in
the form and it worked. When I went to enter the 3rd record in the form it
would not let me type any numbers in the date field. My num-lock is on, all
of the properties are set for data entry, nothing has been changed. It just
stopped working. Has anyone else had this issue and no how to recover from
this problem. I really don't want to start over again. Please
help!!!!!!!!!!!!!!!11

"please help" wrote:

Please help

Try Tools.. Database Utilities... Compact and Repair Database. You
might have some uncollected "garbage" sitting around with all the
changes you're making.

If that doesn't help, please open the Query. Does it have the * "new
record" row at the bottom? If not, then the query itself is not
updateable. If that's the case, open it in SQL view and post the SQL
text here. Indicate which field is giving you the problem.

John W. Vinson[MVP]

I did open the query as you suggested and the * is grayed out. Just as you
said it I can't insert a new record. I did try to compact and repair the
database and that did nothing. I did paste the sql from the query below and
it is the table.prod.workofdate that seems to be giving me the issue.


tblprod.NumberOfEPUEntriesProcessed,
IIf([numberof9810epuitems]=0,0,[numberof9810epuitems]/[total epu hours]) AS
[EPU Thru Put], tblprod.Total9810ESUMinutes, ([total9810esuminutes]/60) AS
[Total ESU Hours], tblprod.NumberOf9810ESUItems,
tblprod.NumberOfESUEntriesProcessed,
IIf([numberof9810esuitems]=0,0,[numberof9810esuitems]/[total esu hours]) AS
[EsU Thru Put], tblprod.TotalOfflineMinutes, ([totalofflineminutes]/60) AS
[Total Offline Hours], tblprod.NumberofOfflineItems,
tblprod.NumberOfOfflineRejects, tblprod.TotalNumberOfflineEntriesProcessed,
IIf([numberofofflineitems]=0,0,[numberofofflineitems]/[total offline hours])
AS [Offline Thru Put], tblprod.NumberOfLookUpMinutes,
([numberoflookupminutes]/60) AS [Total Look-up Hours],
IIf([numberoflookupitems]=0,0,[numberoflookupitems]/[total look-up hours]) AS
[Look-ups Thru Put], tblprod.TotalCheckStrippingMinutes,
([totalcheckstrippingminutes]/60) AS [Total Check Stripping Hours],
tblprod.NumberOfItemsStripped,
IIf([numberofitemsstripped]=0,0,[numberofitemsstripped]/[total check
stripping hours]) AS [Checkstripping Thru Put],
tblprod.TotalNumberofPowerEncodeMinutes,
([totalnumberofpowerencodeminutes]/60) AS [Total Power Encode Hours],
tblprod.NumberOfItemsPowerEncoded,
IIf([numberofitemspowerencoded]=0,0,[numberofitemspowerencoded]/[total power
encode hours]) AS [Power Encode Thru Put],
tblprod.TotalMinutesCleaningMachines, ([totalminutescleaningmachines]/60) AS
[Total Hours Cleaning Equipment], tblprod.TotalRescanMinutes,
([totalrescanminutes]/60) AS [Total Hours Rescanning],
tblprod.NumberOfItemsRescanned,
IIf([numberofitemsrescanned]=0,0,[numberofitemsrescanned]/[total hours
rescanning]) AS [Rescan Thru Put], tblprod.TotalWorkStagingMinutes,
([totalworkstagingminutes]/60) AS [Total Work Staging Hours],
tblprod.TrainingMinutes, ([trainingminutes]/60) AS [Total Training Hours],
tblprod.OtherMinutes, ([otherminutes]/60) AS [Total Other Hours],
tblprod.Comments, tblprod.GracePeriod, tblprod.TotalCourierEscortMinutes,
([totalcourierescortminutes]/60) AS [Total Courier Escort Hours],
tblprod.NumberOfEscorts,
IIf([numberofescorts]=0,0,[numberofescorts]/[totalcourierescortminutes]) AS
[Average Minutes Per Courier Escort],
([numberofprimepassentriesprocessed]+[numberofrehandleentriesprocessed]*10)
AS [Prime & Rehandle Distribution time], ([numberofEPUentriesprocessed]*1) AS
[EPU Distribution time], ([numberofesuentriesprocessed]*3) AS [ESU
Distribution Time],
([total3890primepassminutes]+[totalrehandleminutes]+[total9810epuminutes]+[total9810esuminutes]+[totalofflineminutes]+[numberoflookupminutes]+[totalcheckstrippingminutes]+[totalnumberofpowerencodeminutes]+[totalminutescleaningmachines]+[totalrescanminutes]+[totalworkstagingminutes]+[trainingminutes]+[otherminutes]+[graceperiod]+[totalcourierescortminutes]+[prime
& rehandle distribution time]+[epu distribution time]+[esu distribution
time]+[offline distribution time])/60 AS [Hours Productive],
([totalnumberofflineentriesprocessed]*4) AS [Offline Distribution Time],
tblprod.NumberOfLookUpItems, tblprod.WorkOfDate
FROM tblemployees INNER JOIN tblprod ON tblemployees.EmployeeName =
tblprod.EmployeeName;


"John Vinson" wrote:

On Thu, 15 Jun 2006 11:06:02 -0700, please help
wrote:

I created a query with several calculations in it. I then created an input
form based on that query. The primary key field is work of date. After
spending hours creating the form and reports, I went to enter 2 records in
the form and it worked. When I went to enter the 3rd record in the form it
would not let me type any numbers in the date field. My num-lock is on, all
of the properties are set for data entry, nothing has been changed. It just
stopped working. Has anyone else had this issue and no how to recover from
this problem. I really don't want to start over again. Please
help!!!!!!!!!!!!!!!11

"please help" wrote:

Please help

Try Tools.. Database Utilities... Compact and Repair Database. You
might have some uncollected "garbage" sitting around with all the
changes you're making.

If that doesn't help, please open the Query. Does it have the * "new
record" row at the bottom? If not, then the query itself is not
updateable. If that's the case, open it in SQL view and post the SQL
text here. Indicate which field is giving you the problem.

John W. Vinson[MVP]

Below are the details of the table that this is based. The workofdate field
does work in the table. ID is now the primary key. I made that the primary
key hoping that I can get the workofdate to actually work, but it still does
not.

ID WorkOfDate EmployeeName HoursWorked Total3890PrimePassMinutes NumberOfPrimePassItems NumberOfPrimePassRejects NumberOfPrimePassEntriesProcessed TotalRehandleMinutes NumberOfRehandleItems NumberOfRehandleRejects NumberOfRehandleEntriesProcessed 3890JamRate Total9810EPUMinutes NumberOf9810EPUItems NumberOfEPUEntriesProcessed Total9810ESUMinutes NumberOf9810ESUItems NumberOfESUEntriesProcessed TotalOfflineMinutes NumberofOfflineItems NumberOfOfflineRejects TotalNumberOfflineEntriesProcessed NumberOfLookUpMinutes NumberOfLookUpItems TotalCheckStrippingMinutes NumberOfItemsStripped TotalNumberofPowerEncodeMinutes NumberOfItemsPowerEncoded TotalMinutesCleaningMachines TotalRescanMinutes NumberOfItemsRescanned TotalWorkStagingMinutes TotalCourierEscortMinutes NumberOfEscorts TrainingMinutes OtherMinutes Comments GracePeriod
1 6/2/2006 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 30
2 6/9/2006 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 30
3 6/10/2006 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 30
4 6/10/2006 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 30

"mnature" wrote:

Did you change the query that your form is based on? What were you doing
just prior to the problem?