Subform Datasheet Stability

  • Thread starter Thread starter John S
  • Start date Start date
J

John S

I have set up a form / subform covering pet owners / pets. The subform uses
a datasheet connected to a temporary table so that I can make use of a save
button, and can do validatoin on datasheet items.

I have been using the above structure without a save button, and found the
arrangement, and particularly the datasheet in the subform very stable.
However, after mucking around with the save button, I's starting to wonder
about the stability of using a save button and a datasheet bound to a
temporary table. Anyone else have experience with this approach?

John S.
Aylmer, PQ.
 
---------- "John S said:
I have set up a form / subform covering pet owners / pets. The subform uses
a datasheet connected to a temporary table so that I can make use of a save
button, and can do validatoin on datasheet items.

I have been using the above structure without a save button, and found the
arrangement, and particularly the datasheet in the subform very stable.
However, after mucking around with the save button, I's starting to wonder
about the stability of using a save button and a datasheet bound to a
temporary table. Anyone else have experience with this approach?
Click to expand...

John,

I have a feeling you're trying to get over 3 corners to next door.

a simpler approach would be a continuous form bound to the real data
table as a subform (and offering all of the Access events
functionality). You could do all validations in the form's
BeforeUpdate event and cancel the save process if needed.

Best regards
Emilia

Emilia Maxim
PC-SoftwareService, Stuttgart
http://www.maxim-software-service.de
 
This may the search for the (unnecessary) "holy grail", and I don't know
much about continuous forms. My recolection from VB is that validating on
individual controls sometimes doesn't work (definitely not bullet proof).
Maybe its different fof Access (I suspect not). We always used a combination
of control level validation and form level validation.

You may be right. Part of the problem I'm sensing is that MS Access is built
around bound forms and controls. and perhaps I'm getting away from that (its
strength). And it is getting complicated. I'll look into the continuous
bound form.

Thanks for your thoughts

John S
Aylmer, PQ Canada
 
---------- "John S said:
Emilia,

I thought I had replied to your comments, but can't find the reply in the
newsgroup.

I'll try again.
Click to expand...

John,

I did receive both your replies, thank you for the feedback. And I'd
like to second Larry's advice to "learn the Access way", I'm sure
you'll have it easier then. I don't know very much about VB, but the
various bound form, control, etc. events are the heart of Access user
interface - and they are reliable. Everything else (with some
exceptions of course) would be an endless attempt to fill the leaks.

Best regards
Emilia

Emilia Maxim
PC-SoftwareService, Stuttgart
http://www.maxim-software-service.de
 
Back
Top