brucemc777
Member
- Local time
- Today, 03:58
- Joined
- Nov 1, 2012
- Messages
- 88
Thank you folks for considering my confusion (or as Alice Cooper once put it, "Welcome to My Nightmare")-
I watched a very nicely done YouTube video of adding a single field record by this vector from LearnAccessByCrystal (who goes slow enough for me to follow). Problem is, i want to add a record with 9 fields and i want it to be done all at the same time (reasonably...). I attempted to do so by having the triggered property call another form with the fields to be filled, then on close saving them, but that just triggers the "On Not In List" event again. And Again. And Again...
When my back recovers from being at this desk all day long i intend to try to use an INSERT INTO instead of the
thinking that maybe the INSERT INTO and possibly a refresh might avoid something about the DoCmd that triggers the "Not In List", and though i doubt it, it is worth a try (as much as i fear my very rudimentary experience at handling quotation marks in an SQL statement to be run via VBA).
Is there a better angle at this?
I am going to have to use the technique in a number of instances (five to ten) because i do not want to have to stipulate that the user first always populate one table (via a form) before they can populate another - i want it to be "inline".
Thank you very much for your expertise! I suspect i will be learning for quite a bit now, for some very knowledgeable people have provided me with examples to try for other issues and i am simply trying to keep my head above water by addressing priorities for now-
I watched a very nicely done YouTube video of adding a single field record by this vector from LearnAccessByCrystal (who goes slow enough for me to follow). Problem is, i want to add a record with 9 fields and i want it to be done all at the same time (reasonably...). I attempted to do so by having the triggered property call another form with the fields to be filled, then on close saving them, but that just triggers the "On Not In List" event again. And Again. And Again...
When my back recovers from being at this desk all day long i intend to try to use an INSERT INTO instead of the
Code:
DoCmd.Close acForm, "frmInputEquipment", acSavePrompt
Is there a better angle at this?
I am going to have to use the technique in a number of instances (five to ten) because i do not want to have to stipulate that the user first always populate one table (via a form) before they can populate another - i want it to be "inline".
Thank you very much for your expertise! I suspect i will be learning for quite a bit now, for some very knowledgeable people have provided me with examples to try for other issues and i am simply trying to keep my head above water by addressing priorities for now-