469,656 Members | 1,837 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 469,656 developers. It's quick & easy.

(A2K) Strange behaviour on datasheet style subform - columns not binding correctly.

I added a new field to a table in the tables database. In the code
database, I added a new column for the new field to a datasheet
subform. I opened it in datasheet view and moved the column to the
position I wanted it. No records are returned by the form's query (it
has a "Where ID = -1" clause and the GoToRecord proc on the main form
changes the subform's recordsource).

When I opened the form and started adding data to the subform, data
from the new column was added to the wrong table field. Also, a proc
that executes an "Insert Into ... " query to do bulk adds put data for
the new column into the wrong field.

The form's query does not use tables directly, but uses them through
aliasing queries. e.g. qselSomething is "Select * From tblSomething".

I decompiled, compacted, recreated the datasheet subform's query and
the problem seems to have gone away.

Has anyone else seen this? Any explanations?

--
Regards.
Richard.
Nov 13 '05 #1
1 2127
I don't use datasheet views, so I'm not sure if this relates, but
occassionally I have found quirky behavior like this in form views. Try
deleting the form's recordsource, compiling and saving the form, then
replacing the recordsource line. Not sure how or why, but it "recompilies"
the form even when a decompile/compile fails to fix the glitch.
Darryl Kerkeslager
"Richard Sherratt" <ri**************@NOTHINGHEREbrunsley.com.au> wrote in
message news:c5********************************@4ax.com...
I added a new field to a table in the tables database. In the code
database, I added a new column for the new field to a datasheet
subform. I opened it in datasheet view and moved the column to the
position I wanted it. No records are returned by the form's query (it
has a "Where ID = -1" clause and the GoToRecord proc on the main form
changes the subform's recordsource).

When I opened the form and started adding data to the subform, data
from the new column was added to the wrong table field. Also, a proc
that executes an "Insert Into ... " query to do bulk adds put data for
the new column into the wrong field.

The form's query does not use tables directly, but uses them through
aliasing queries. e.g. qselSomething is "Select * From tblSomething".

I decompiled, compacted, recreated the datasheet subform's query and
the problem seems to have gone away.

Has anyone else seen this? Any explanations?

--
Regards.
Richard.

Nov 13 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

4 posts views Thread by MacDermott | last post: by
2 posts views Thread by LaurenW | last post: by
1 post views Thread by s_wadhwa | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.