Prev: Compile error: Argument not optional
Next: Creating a string based on a query
From: BrianDP on 13 Apr 2010 18:50
This is a very strange one. I have several forms attached to this
form, [service orders]. There are several subforms (5 to be exact)
-- Subforms for: Customer Address, SO line Items, Machine/Group
Subform, and a couple other subforms.

When I save the main from, [service orders], the SO Line items subform
changes to the Service Orders form, and, because it's trying to
reference itself, it just shows blank. If you open the form in
design, and type the correct name of the subform, it suddenly displays
correctly. You can even pop it into Edit mode! You can change
records, and the subform displays correctly. If you try to save the
from though, the subform goes haywire again.

Another one of the attached forms is also acting incorrectly, it's a
simple attached table, with an [ID], A Link back to the master table
[SOParent], a Text field [Jobno], and a link to another table, a
lookup table for Groups. The link is the 3rd field over, and that is
the bound field for the drop down, but the drop down doesn't display
correctly. I'm not sure if either of these two things are related.

One more thing- I am using Access 2002 to develop this. For a while
today I was forced to go to another computer for a while, and that
computer is running a much much newer version of access - The version
with the Ribbon? Is that Access2010 or something? When I opened it,
it didn’t say that it was going to “upgrade” or convert it to another
version of the database. Anyway, in the new version of access, I know
the [group] subform worked. I don't think I was having these problems
problems at all on the NEW version of access. It was when I brought
the mdb back to the 2002 version. I guess I should find an older
version of the file, but I did some programming that I'd rather not
have to re-do.

For sure this tells me that I don't want to upgrade to that newer
version of access. For one thing, those ribbons, and the way they've
moved everything around is a bad thing - at least for someone who is
way entrenched in the older Access. (I'm not turning this into a
debate on 97/2002/??) For sure we needed to move from 2002 to 97,
and, I think there is enough to warrant moving from 97 to 2002, but
this last leap is too much. Feh.

If anyone knows of anything that would cause the behavior I've
described here, please let me know. I can answer more questions, or
make the form available if someone needs.

Thanks in Advance,
-Brian P.





From: BrianDP on 14 Apr 2010 16:49
<<Subform Losing it's links - changing to completely different form!>>

The form was named [SO Editor], and the detail file which was getting
detached was [SODetail Sub] One of my co-workers was looking at the
problem with me, and we came up with the idea of changing the form/
subform name. Not really knowing why, or what would happen.

Excet that NOW, it's working. I've saved the form several times and
not once has is switched the form out for a different one! It's
working now! All I had to do was change the form name, and the
subform name, and it works again.

If anyone knows WHY this happened, I'm still very interested to have a
WHY to go with my ffix!
 | 
Pages: 1
Prev: Compile error: Argument not optional
Next: Creating a string based on a query