Thomas

As it knows all the keys I'm interested in including all conditions it should be much faster than any programmed logic.

This is an incorrect assumption. ProvideX SELECT is *not* SQL SELECT

You are right about SQL SELECT where the SQL engine chooses the best possible path to get to the data based on various criteria including the WHERE clause -- and it will be fast as long as you have indexed the columns on which you're selecting.

ProvideX SELECT is some syntactic sugar which allows you to easily code a file read loop
You can use a file channel or a file name. If you use the latter, the file will be closed after the last NEXT RECORD iteration
However :
- You must select yourself the best KNO to access the data. ProvideX won't do it for you
- If you use a file channel, the SELECT will start the loop at the current cursor position in the file, unless you use the BEGIN clause to specify the first key to read (this is the same as the Cobol START statement)
- Adding a WHERE allows ProvideX to execute the logic inside the SELECT/NEXT RECORD loop for only the records that match the conditions. Basically the IFs are done at the C-level therefore they are faster. If you don't specify a WHERE then the loop will be executed for all the record between the BEGIN (if any) and END (if any) clauses

Hope this helps

Hi Gord


Long time no talk, hope you're doing well
Would definitely like a VSCode implementation as it is already my editor of choice for almost all non-PVX coding
Depending how such an extension is done, I could even contribute (I think I could still write some decent C# code...)

Hi
Up until PxPlus 2022, projects metadata were stored in KEYED files *plus/proj/wkids.dat and *plus/proj/wkseq.dat
A change had been made in recent years to allow those files to be LINK files pointing to another location to be able to retrieve projects when upgrading PxPlus
I understand PxPlus 2023 changed this to a more traditional way with a folder and a dedicated settings file (like package.json for NodeJS projects and composer.json for PHP projects)
This is great. But apparently it means that I have to re-create all the projects I had set up (not so many fortunately), since I copied the two LINK files from my pxp2022/lib/_plus/proj folder to the same location in my pxp2023 installation, and no automatic migration happened, I have only the "default" project in the IDE.
Again, not a big issue, just something that would be useful -- either an automatic process first time the project maintenance is opened, or an additional option to run once in the utility that was previously used to create the LINK files
My 0.02 €

Hi Jeff

Is that what you're looking for ?
->preview=new("*viewer/preview")
->? preview'*
AlwaysUseDefaultOpenPath,Banner,Bottom,Caption$,Close(),Collate,Color,Colour,Col
umn,Columns,Copies,DPIPrinter,DPIScreen,DefaultFixedFont$,DefaultFixedFontSize,D
efaultOpenPath$,DefaultOrientation,DefaultOrientation$,DefaultPaperSize,DefaultS
aveAsPath$,Delete(),DisableBanner,DisableDelete,DisablePrint,DisableSaveAs,Disab
leSearch,DisableWatermarks,Event(),FileName$,Find(),FindNext(),FindPrevious(),Fi
rstPage(),GotoPage(),HelpContents$,HelpFile$,HelpIndex$,Icon$,Init(),Language$,L
astPage(),Left,LookAndFeel,MinimumColumns,MinimumRows,NextPage(),Open(),OutputEv
enNumberOfPages,Page,PageGutterHorizontal,PageGutterVertical,Pages,PaginationAt,
PreviousPage(),Print(),Printer$,PrinterDescription$,Process(),Quit(),Range$,RePa
int(),Report,Right,Row,Rows,SaveAs(),SaveAsPDF(),ScaleToFit,ScrollDown(),ScrollL
eft(),ScrollRight(),ScrollUp(),SetCallBack(),SetWindowStateOnCreate,SetWindowSta
teOnFirstPage,SetWindowStateOnSpoolComplete,SetWindowStateOnSpoolStart,Software$
,SuppressAllBlankPages,SuppressBannerInfo,SuppressFirstBlankPage,SuppressPrinter
Selection,SuppressSplashScreen,SuppressStatusBar,SuppressToolBar,SuppressToolTip
s,SuppressWaterMarks,ThemeName$,Top,UsePrinter$,Version$,View,View(),Visible,Wat
erMark,WaterMarkPages,Zoom,Zoom(),ZoomIn(),ZoomOut(),_revision$,

Regards

Hi
My boss found the issues in the attached image while doing some code

I've tried some variations with parentheses to transform variables into values but still getting the error 20

Hi
Up to 4 years ago, the Apache interface used to be compatible with IIS as well and there were some information about it in the « Running on the web » section of the doc IIRC.
It looks like this information has been moved to the Webster+ docs at
https://manual.pvxplus.com/PXPLUS/Webster/Webster%20Setup.htm#iis_setup
Basically you need to create a CGI handler for the .pxp file extension in IIS, and give all you web-based programs this common extension, and you should be good to go.
Hope this helps

Hi

There is a minor issue in *obj/xml with the find_node() method

-}x=new("*obj/xml","<prestashop><products><product><id>1</id></product></product
s></prestashop>")
-}
-}xpath$="prestashop/products/product/id"
-}? x'find_node(xpath$)'value$
1
-}?xpath$
prestashop

I can work around by sending the parameter by value with parentheses or as an expression such as xpath$+""

But I think it should be handled in the method itself by protecting the _tag$ input parameter

TIA