My son's business has both a retail and a wholesale component. My A5 application migration from V1 to V11 is almost complete. I now have to deal with a nice feature that V1 provided, "Application Cards".
When my son started his wholesale operation I copied all the A5 files to a new directory, and emptied out all the tables. All filenames remained the same. I created an application card for the new directory (in V11 I've learned that we use forms for menus instead of application cards).
So ... on his V1 application card I put a button that says basically, go to the wholesale directory and bring up its menu. This enabled a seamless crossover to the other directory and both menus worked concurrently. He could create an invoice for a retail customer side by side with a wholesale customer's invoice. Alpha 5 kept track of which directory was involved and there never was a problem.
I don't know V11's nuances but I do know that it's a major pain in the butt to have to close down the first workspace to do something in the second workspace and then come back again. That's a great example of the opposite of "seamless".
Alphaholics, is there hope for my son? Do you have a trick up your sleeves?
For those of you who managed to escape V1, this implementation was via an "app_run" capability.
Thanks for listening. Please have a solution. --- Sam
When my son started his wholesale operation I copied all the A5 files to a new directory, and emptied out all the tables. All filenames remained the same. I created an application card for the new directory (in V11 I've learned that we use forms for menus instead of application cards).
So ... on his V1 application card I put a button that says basically, go to the wholesale directory and bring up its menu. This enabled a seamless crossover to the other directory and both menus worked concurrently. He could create an invoice for a retail customer side by side with a wholesale customer's invoice. Alpha 5 kept track of which directory was involved and there never was a problem.
I don't know V11's nuances but I do know that it's a major pain in the butt to have to close down the first workspace to do something in the second workspace and then come back again. That's a great example of the opposite of "seamless".
Alphaholics, is there hope for my son? Do you have a trick up your sleeves?
For those of you who managed to escape V1, this implementation was via an "app_run" capability.
Thanks for listening. Please have a solution. --- Sam
Comment