By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
459,472 Members | 1,168 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 459,472 IT Pros & Developers. It's quick & easy.

One form - 2 tables?

P: n/a
I have a form with 3 textboxes : txtname, txtdate, txtcolor
txtname and txtdate have to be saved in tblactivity
and txtcolor has to be saved in tblcolors
So one form with txtboxes has to fill two different tables. Is that
possible??
I can't or won't use a subform, nor can i use a query. Because it's
one form for 12 different tables and one tblcolor. So when i click on
my mainform with 12 buttons, i load the table in the form depending on
the name of the button.
(I hope i make any sense)

Its more than only this, i simplyfied it a lot.

Only vb code for access 97, please.

TX Anyone, anyway, anywhere, anyhow.
Nov 13 '05 #1
Share this Question
Share on Google+
2 Replies


P: n/a
You can read here about unbound forms:

http://www.accessdatabasetips.com/forms.html
Best regards,
J. Paul Schmidt, Freelance Access and ASP Web Developer
www.Bullschmidt.com
Classic ASP Design Tips, ASP Web Database Demo, ASP Bar Chart Tool...
Nov 13 '05 #2

P: n/a
da*********@pandora.be (Peter D) wrote in message news:<2f**************************@posting.google. com>...
I have a form with 3 textboxes : txtname, txtdate, txtcolor
txtname and txtdate have to be saved in tblactivity
and txtcolor has to be saved in tblcolors
So one form with txtboxes has to fill two different tables. Is that
possible??
I can't or won't use a subform, nor can i use a query. Because it's
one form for 12 different tables and one tblcolor. So when i click on
my mainform with 12 buttons, i load the table in the form depending on
the name of the button.
(I hope i make any sense)


Why 12 different tables? Do they have different structures? Why not
save a "flag" field so you can identify the "grouping" or whatever
each record in the table belongs to? MUCH easier. Otherwise, you'd
have to unbind the txtColor field and use the BeforeInsert event to
write the value to the second table. PITA. And what if you update
that value in your form? not fun.

Why exactly do you need to put all this information into 12 different
tables? is there something here that a simple parameter query won't
solve?
Nov 13 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.