Loren

You may want to try the IZ parameter as well, to have your program ignore any memory size limitations

Regards

Thomas

Since you need both icons and text with different font styles, I see several ways to do this :

- An easy one :
Define the buttons using graphical mnemonics (an image, two fonted texts and a frame with rounded corners) and then use SETMOUSE to define the clickable region and the CTL it should return. However it won't handle the hover event to change the button background color...

- A more complex one :
Define the buttons as bitmap buttons and use a virtual bitmap (using the *bitmap* special file) that you create yourself.
This way you can have the hover event handled

Regards

Hi


Best wishes for 2022 to all


I cannot remember if there is any system parameter that would prevent PxBasic V10 to overwrite the [Pvxprg] header (as created by Sage PVX v9.10) with [Pxpprg]
This way I could use PxBasic's *IT editor to do some coding in the old app I have to maintain and programs would still be readable & executable by ProvideX


TIA

Skip

I know at one point (in the 2000s, when ProvideX swung between the Sage and Best Software brands) there were classes to learn the language, an intro to Nomads and an Advanced Nomads course, as well as some OOP introduction.
I even found some old Sage & Best training / tutorials Word docs in my archives
An awful lot of things have changed since, but they would probably be still relevant for the most part

However I guess these docs (or up-to-date versions of them) are only available if you purchase some kind of training class with the experts

You need to check with your distributor if they offer this type of service, and if not, ask the PxPlus folks.

Regards

Hi Jeff


Haven’t done much Crystal and PxPlus ODBC, but :
How about linking order lines to order header and inventory master ?
Would be two inner joins to the main table instead of one left join then one inner join


Just thinking out loud


Regards,

Hi


I migrated an hospitality software from Tbred 8.3 to ProvideX 4.01 in 1998.
At that time, the migration tool was creating a big bundle text file with all your programs and data files (depending on the directory devices you had selected for migration)
You then moved this big ass file to the target environment / system and used the unbundle tool to recreate programs and files in ProvideX format.
Almost all incompatibilities were addressed by the conversion tool, and fixing those that remained only took hours (do not have the details, as it has been 23 years). Even if you were using the Tbred « Windowing » system which we did not, and is quite different from ProvideX windows and dialogue controls, the conversion tool was modifying your code to call emulation routines provided by ProvideX.
During the transition period, you can use the various emulation modes provided by ProvideX (such as the Tbred FID() format, the windowing emulation, etc…) but it is then recommended to change your code to move and stick to the ProvideX standards and conventions. Who would want to migrate to another BB once under ProvideX anyway ?


You can read more @ https://manual.pvxplus.com/PXPLUS/conv.tbd/overview.htm


Hope this helps

Here are a couple of issues I found while using the FM generation wizard :

1) Inserting a dot in the FM panel name
If I name the panel with a dot (e.g. company.fm), I cannot re-open the FM wizard after the first generation of the panel. From the Nomads selector I get a message telling me to delete and regenerate the panel. From *it, I can open the library then edit the generated panel.
If I name the panel with an underscore (e.g. company_fm) then everything works as expected.
Looking at the Nomads code, this is due to the way the folder tabs are generated.
So I would simply suggest to add a check on the presence of a dot (.) in the name when creating a new FM object

2) Defining a primary key segment with a format specifier
If one of the primary key segments in the data dictionary is defined as "Last Substring" (for example), then I cannot complete the FM wizard
I am getting a message saying that some of the required fields are missing on the screen layout.
This is because the :[...] format specifier adds an extra comma to the IOLIST and screws up the test @ 1446 in fm_wizard

Regards