Hello from this newbie member. I hope the above post title accurately describes my little problem.
- Underlying table name = Booktext ---- relevant field = booktext1
- basic input form name = simple Form Booktext Query choose edit range [call it form1 for simplicity sake]
- second input form name = FieldBooktext2expanded [call it form2 ....]
- (not relevant, just for info) each record is based on a numbered field "pararef" (not an auto number field) so the book is sorted/ordered to this manually assigned text field
forms 1 & 2 are both based on table Booktext and are both open at the same time and update of relevant field booktext1 occurs as explained below (I have been unable to work out a good/elegant method of achieving what I want ...).
Processing/intent: form 1 is the main/basic input form of text for my book. It has the input field booktext1 which updates the Booktext table. This field cannot take up much of the visible screen space in form1 (for reasons too complicated to explain here) and so sometimes (fairly often) it's content is greater than what can be seen on screen. I get sick of having to move the sidebar handles to see the text at the bottom of the field. So for convenience, I have this routine - double click of field booktext1 in form1 opens form2 which has a full screen version of the input field booktext1. That's fine, works OK. But when I come to save form2 it of course.
The processing "flow" (simplified) is as follows: Open form1, go to relevant existing pararef (or create a new one); type material into field booktext1; decide I want to use/type stuff into form2; open form2 by double clicking field booktext1; type stuff into form2 booktext1 field; save form2 input; view book report for that pararef based on what I've input/saved;
I have experimented a little with close/save of form1 after opening form2 to pararef = to form1's pararef and/or using setvalue for pararef but seem to run into trouble. so I thought it simpler to go to the Access gurus rather than waste any more time on what (I am sure) is a simple fix.
Using MS Access 2007 on a Win 10 64 bit machine. Hoping someone can help ....
EdKerm