Data input in one field bleeds into another

I have a form with two text fields, and when I input information in one, a
piece of it breaks off into the second field. When I correct the second
field, it corrupts the first field.
e.g.-- first field should read "9 AM-12 PM, 1 PM-4 PM" and second field
should read "Teaching Tolerance Through Drama" but it reads as "Teaching
Tolerance Th9 AM-12"

When I fix the title, the time reads "(box)(box)1 PM-4 PM"

The fields are not linked nor are they based on calculations or anything
like that. Any ideas?

Do you by any chance have both fields record source set to the same field
from the data source?

--
HTH

Mr B
askdoctoraccess dot com


"troublecat12" wrote:

I have a form with two text fields, and when I input information in one, a
piece of it breaks off into the second field. When I correct the second
field, it corrupts the first field.
e.g.-- first field should read "9 AM-12 PM, 1 PM-4 PM" and second field
should read "Teaching Tolerance Through Drama" but it reads as "Teaching
Tolerance Th9 AM-12"

When I fix the title, the time reads "(box)(box)1 PM-4 PM"

The fields are not linked nor are they based on calculations or anything
like that. Any ideas?

The behavior you desribe really sounds like both controls are bound to the
same underlying table column. Open up properties window for each and check
to see how it is bound.

However, The box/box you referenced may be the tip off of the real
situation. It sounds like the way Access displays non-printing characters.
Is your data imported from some other source? Perhaps you have tab characers
in there? Or it came from a source that supported multiple lines? To see,
open up the underlying table and find a record. Then expand the vertical
size of the display row in table view by putting the mouse on the break
between the record selector buttons on the left. When it is possitioned
correctly, the mouse pointer will change to a horizontal bar with a
double-headed arrow (Up/Down). Drag the divider down to at least double the
vertical height of the row. Now look at the field - does it have a second
line of data in it where it doesn't belong? For example, perhaps your course
title raw data had the course name, then a CRLF and then the time the course
is given, and when imported it came into the single field but you haven't
seen it prior to now.

Neither of these is the case. The two fields are bound to separate columns
of data and the data isn't being imported from anywhere--I am inputting it in
the form. However, as soon as it's entered, the data that's input gets
garbled and shows up incorrectly in both the form and the underlying table.


"NKTower" wrote:

The behavior you desribe really sounds like both controls are bound to the
same underlying table column. Open up properties window for each and check
to see how it is bound.

However, The box/box you referenced may be the tip off of the real
situation. It sounds like the way Access displays non-printing characters.
Is your data imported from some other source? Perhaps you have tab characers
in there? Or it came from a source that supported multiple lines? To see,
open up the underlying table and find a record. Then expand the vertical
size of the display row in table view by putting the mouse on the break
between the record selector buttons on the left. When it is possitioned
correctly, the mouse pointer will change to a horizontal bar with a
double-headed arrow (Up/Down). Drag the divider down to at least double the
vertical height of the row. Now look at the field - does it have a second
line of data in it where it doesn't belong? For example, perhaps your course
title raw data had the course name, then a CRLF and then the time the course
is given, and when imported it came into the single field but you haven't
seen it prior to now.

1) Do you have any event procs associated with either of the text box
controls? (Right click a control, select PROPERTIES, select EVENTS tab)
Perhaps an "OnExit" proc got in there in error.
2) If you create a very simple "throw-away" form that just has the minimal
bound controls do you get the same behavior?
3) Is the data bound to a back end other than MS Access, such as, say a SQL
Server database that may have a stored proc associated with the record?
4) Does it happen if you go to TABLE view of the table and enter data that
way?

"troublecat12" wrote:

Neither of these is the case. The two fields are bound to separate columns
of data and the data isn't being imported from anywhere--I am inputting it in
the form. However, as soon as it's entered, the data that's input gets
garbled and shows up incorrectly in both the form and the underlying table.