ScreenIO - tabbed screens
Posted: Thu Jun 23, 2016 11:16 am
Hi all,
I know that some of you are using tabbed screens with ScreenIO (Steve and Gabriel, at least). I am going to put together a really big program that ties a lot of screens together. SOME of them are update screens that represent different sections of ONE SINGLE data file record. Others do things like look-ups on customer history, issuing documents, and create/update records in other files, but they are all keyed by one customer account number.
Assume that screens (tabs) #1, #2 and #3 each operate on different parts of the same data record. When I click on each tab, is it better to open/read/save the record inside of each tab before moving to the next? What if I want to keep all of the fields "open" across the tabs and then have the SAVE button on only the first screen? Would I have to pass the data back and forth across the tabs using Mat MYF$ and Mat MYF? How do you keep track of whether changes are made (or not) in screen #2 or #3 when you go back to screen #1 where the SAVE button is? Or do you not reread the record for each tab at all? And to make it more complicated, on the first screen is a status section that in part, summarizes some of the data on the later screens. For instance, if someone is in bankruptcy, all of that information might be in screen #3, but on screen #1, there is a notification "Bankruptcy" so that the user can quickly tell.
I know that a separate open/read/save on each tab is probably easier, but if I'm working on a brand new customer and someone saves screen #2 (with only secondary data on it) and then exits without saving screen #1 where the customer number and name are supposed to be entered, I would be in trouble. I'm confused how to navigate tabbed screens when they are all parts of the same record. There are too many fields to fit easily on one screen so I'm trying to break it up logically.
Any hints would be welcome. Thanks.
-- Susan
I know that some of you are using tabbed screens with ScreenIO (Steve and Gabriel, at least). I am going to put together a really big program that ties a lot of screens together. SOME of them are update screens that represent different sections of ONE SINGLE data file record. Others do things like look-ups on customer history, issuing documents, and create/update records in other files, but they are all keyed by one customer account number.
Assume that screens (tabs) #1, #2 and #3 each operate on different parts of the same data record. When I click on each tab, is it better to open/read/save the record inside of each tab before moving to the next? What if I want to keep all of the fields "open" across the tabs and then have the SAVE button on only the first screen? Would I have to pass the data back and forth across the tabs using Mat MYF$ and Mat MYF? How do you keep track of whether changes are made (or not) in screen #2 or #3 when you go back to screen #1 where the SAVE button is? Or do you not reread the record for each tab at all? And to make it more complicated, on the first screen is a status section that in part, summarizes some of the data on the later screens. For instance, if someone is in bankruptcy, all of that information might be in screen #3, but on screen #1, there is a notification "Bankruptcy" so that the user can quickly tell.
I know that a separate open/read/save on each tab is probably easier, but if I'm working on a brand new customer and someone saves screen #2 (with only secondary data on it) and then exits without saving screen #1 where the customer number and name are supposed to be entered, I would be in trouble. I'm confused how to navigate tabbed screens when they are all parts of the same record. There are too many fields to fit easily on one screen so I'm trying to break it up logically.
Any hints would be welcome. Thanks.
-- Susan