JohnHarkins
MIS
Hi!
My client hated the design I created using normalized tables and complementary forms to navigate and pop up various related information. I had a continuous form that kept everything on the main form that would fit without scrolling and then used a command button to get at additional data.
Instead, she wants a "spreadsheet" that opens up with the scroll bar several columns to the right (haven't a clue how to do that, but figure it must be something related to a property of OpenForm or loading). After that the challenge is to handle items on this spreadsheet that are really kept in lookup tables and still allow changes to such items (additions, changes, insertions, deletions). I've thought of using some "quick scroll" buttons at the bottom (footer?) of the form to go to the various sections.
What techniques can I employ? Is there any hope of convincing the client that my design will afford better performance in a mult-user environment?
I have the feeling that this is really a custom form and not a datasheet or continuous form in the traditional sense, but I'm probably too much of a novice to be able to articulate the issues properly.
Thanks for your guidance.
John Harkins
My client hated the design I created using normalized tables and complementary forms to navigate and pop up various related information. I had a continuous form that kept everything on the main form that would fit without scrolling and then used a command button to get at additional data.
Instead, she wants a "spreadsheet" that opens up with the scroll bar several columns to the right (haven't a clue how to do that, but figure it must be something related to a property of OpenForm or loading). After that the challenge is to handle items on this spreadsheet that are really kept in lookup tables and still allow changes to such items (additions, changes, insertions, deletions). I've thought of using some "quick scroll" buttons at the bottom (footer?) of the form to go to the various sections.
What techniques can I employ? Is there any hope of convincing the client that my design will afford better performance in a mult-user environment?
I have the feeling that this is really a custom form and not a datasheet or continuous form in the traditional sense, but I'm probably too much of a novice to be able to articulate the issues properly.
Thanks for your guidance.
John Harkins