Hello

It looks like the libmysql.dll that comes with the latest MySQL 8.0.xx version is 64-bits only and does not work with PxPlus 2019.

I kept on getting an "Unable to load libmySQL.dll" message when trying to open a [mysql] channel
It finally worked when I grabbed a 5.7.25-win32.zip from mysql website, extracted the .dll from and overwrote the 64-bits one I had put in the pxplus folder.

Is it the way this is supposed to work ?
Any plan to update PxPlus to be compatible with the latest MySQL version ?

Thanks

Thanks Thomas !

Peter

After a few years I started using labels similar to what Visual Studio generates for event handlers so that PVX newbies coming from more mainstream languages would be less lost
;<PanelName>_Loading for PRE_DISPLAY
;<PanelName>_Shown for POST_DISPLAY
;<PanelName>_Closing for ON_EXIT
I also started appending control types suffix instead of prepending them (Close_BT instead of BT_Close) for the same reason

Having some place in Nomads global settings to define those coding standards would be a nice addition, BTW.

I was usually hiding the grid while formatting and loading it, then showing it again when done.
You should also check out the '-U' and '+U' mnemonics although I don't remember if they have any effect with the grid refresh

Jeff

How about setting CONTENT_TYPE$ to application/json and
either EXIT_TEXT$ to your JSON error message
or write your JSON data to %print_fn ?

Dave

An Office 365 subscription allows you to get an always up-to-date version of MS Office (currently Office 2016) and to connect the Office apps to your outlook.com email address thus allowing you to easily save documents to the cloud via OneDrive. You still get a local copy of the Office apps on your local computer and you are still able to connect to it using the DEF OBJECT WordObj,"Word.Application".

If your users are using the on-line version of the Office apps through their browser (the equivalent of the Google Docs apps) then you won't be able to interface them like the local copies. Not sure Microsoft publishes an API that would allow you to send HTTP requests and create cloud docs in the user's One Drive account. This used to be possible with Google Docs, though...

Hope this helps,

Sam

Microsoft .Net has been around for a long time now. When you code .Net apps, you can use any language you want -- C/C++, VB.Net, C#. C#, some hybrid of C and Java (development codename COOL for C Object Oriented Language), would be your language of choice. What you write is translated into IL (Intermediate Language) by the CLR (Common Language Runtime, a kind of virtual machine), and then compiled in machine code for the target OS version the first time you run it on the target machine, by the JIT (Just-In-Time) compiler. As you may have already thought, this shares a lot of ressemblance with Java -- that's for a reason, Microsoft borrowed a lots of things from Java when designing .Net and C#. Also, IL is a byte-code, so that should ring a bell as well : that looks a lot like tokenized programs run by an interpreter that is specific to the target platform : Write Once, Run Everywhere

Almost 30 years ago when I learned UNIX, I was told this motto : everything is a file. .Net's motto, like most modern-days language, is : everything is a class. When you create a .Net console program, you create a class that will run from the console. When you create a WinForms app (the grey windows running on the desktop), you create a class that will derive from the standard .Net Windows Form class. Same thing for ASP.Net and MVC.Net when creating web apps.

PxPlus knows how to interface with ActiveX/OLE/COM classes, which are classes/objects built using pre-.Net compiled languages (generally C/C++, sometimes VB6, Delphi or whatever).
By default, when you create a .Net class, it is not visible by the outside world (your ProvideX code) through the COM interface. You must "decorate" your class with special clauses so that it is made COM-visible at compilation time and thus a COM-enabled environment like PxPlus can access it, instantiate an object and use its properties, methods and events.

I would say that "Direct .Net support" probably means that you can access a .Net class without it being COM-enabled. That would be great because you could not only use utility .Net classes made by third-party vendors (for exemple, the Crystal Reports interface) but also the FCL (Framework Classes Library) which is a bunch of classes written by Microsoft for all kind of purpose.

I'll let the PxPlus folks answer about their plans with .Net direct support

Scott

At my first employer we had an hospitality software package written in Tbred that we converted to ProvideX and PxPlus and GUI-fied. At the moment, I believe the nth-purchase of the company by a bigger fish (Infor) has been fatal to the PxPlus based package (although my old colleagues had migrated it under iNomads with an SQL backend) as it is now not sold anymore nor enhanced, and support won’t last much longer (developers are being let go one after the other).

That being said I believe there are hospitality software packages on the north-american market. Jonas Software has one if I am not mistaken. I remember also something called Five Stars Hotel Systems. There are a few others.

Hope that helps