Data is populating the same in EVERY record in the DB

[Guest]

I'm trying to assist a user who changed the name of a field in a form. After
doing so, the information she enters into the field populates in EVERY
record in the DB. Does anyone have any ideas on the cause of this and how to
correct it? I know absolutely nothing about Access (or any other DB for that
matter).

 

[Guest]

Without more details there is not much advice you can get.

but

I'm trying to assist a user who changed the name of a field in a form.
I know absolutely nothing about Access (or any other DB for that
matter).

Sounds a little strange to me

 

[John W. Vinson]

I'm trying to assist a user who changed the name of a field in a form. After
doing so, the information she enters into the field populates in EVERY
record in the DB. Does anyone have any ideas on the cause of this and how to
correct it? I know absolutely nothing about Access (or any other DB for that
matter).

Forms don't HAVE fields - that would appear to be the problem! This user
changed the name of a textbox on a form, I'd guess - and data is not stored in
forms, but only in Tables. You now have an "unbound" control on the form, not
connected to any table; so the value isn't being stored *anywhere at all*,
just displayed repeatedly on the form.

For help fixing this, please open the form in design view and post the
following properties:

The Form's Recordsource (post the SQL view of the query if it's a query, the
relevant fieldnames if it's a table)
The textbox's Name and Control Source properties


John W. Vinson [MVP]

 

[Guest]

John,

Thanks for the reply. However, we have what appears to be a symantics
issue here. Not knowing anything about Access, I may not be using the right
terminology, so let me try to explain as best I can. The user has a form.
In that form is a blank box to enter data - I would consider that a "field".
So, the form does have what I would consider to be a field. Next to that
"field" is the name of the "field". She changed that name from something
really long, to just "Date". Since then, when she enters the date into that
"field" (which of course the actual data is stored in the DB itself), it
populates that same date in every single record in the DB. Does that help
explain it more clearly?
--
Thanks,

Todd

 

[Pieter Wijnen]

yes,
She's put a reference to the Date Function =Date() in The ControlSource
instead of to a Field in a Table
FYI, Forms & Reports have Controls, Which might be tied to Table/Query
Fields

Pieter

 

[John W. Vinson]

John,

Thanks for the reply. However, we have what appears to be a symantics
issue here. Not knowing anything about Access, I may not be using the right
terminology, so let me try to explain as best I can. The user has a form.
In that form is a blank box to enter data - I would consider that a "field".
So, the form does have what I would consider to be a field. Next to that
"field" is the name of the "field". She changed that name from something
really long, to just "Date". Since then, when she enters the date into that
"field" (which of course the actual data is stored in the DB itself), it
populates that same date in every single record in the DB. Does that help
explain it more clearly?
--

Ok, jargon again.

Data is stored in Fields in Tables. That is the *ONLY* place data can be
stored permanently.

A Form is just a tool, a window which lets you manage the data that's stored
in your tables.

Tables have fields; Forms have Controls (textboxes, or other types of controls
such as checkboxes, combos, etc). These controls will usually be bound to
table fields, but can also be unbound.

If your user changed the name of a control on a form, that shouldn't cause the
effect that you're seeing. My guess is that the user changed the Control
Source of the control to something that is *NOT* the name of a field in the
table.

Three requests:

1. Open the Table itself (not the form). Does this field have repeating
values? Null values? Do you see the same date in the Table as you do on the
form?
2. Open this form in design view. View its Properties. What is the
Recordsource property (the first property on the data tab)? If it's a SQL
string or a Query, please post the SQL.
3. View the properties of the textbox. What are the Name and Control Source
properties?


John W. Vinson [MVP]