Jeff

Thanks for bringing this to our attention.  You should be able to put the LIKE compare inside parenthesis and it will work.

We will address this on the next build.

First off we STRONGLY recommend that you use current support versions of PxPlus.  Version 5 of ProvideX came out in 2001 -- that is 18 years ago and predates even Windows XP.

Next the ProvideX or "Installation Key" shipped with your order only activates enough of the system so you can perform an online product registration within 30 days of the date of install.  The install key is only temporary and ultimately you will need to get a permanent key by registering the product.  NOTE: You can enter all keys supplied with your product to temporarily enable the full functionality purchased for 30 days or until you register the install.

Registration of the software is done online.  PxPlus comes with the tools required to do an online registration, whereas for ProvideX you need to download the online registration tools.  Details on how to download/install these tools can be found at:  https://home.pvxplus.com/pgsrvr.pvp?pg=providex_activation

Again, using old unsupported ProvideX or PxPlus software is NEVER recommended.  Over the years we have made numerous changes to adapt to newer operating systems.  Running versions of ProvideX/PxPlus on operating systems that did not exist at the time of their release can result in unforeseen problems.

Josh

I have been looking into adding a JSON output method to the XML object.  There are however a few challenges as not all XML and JSON structures can be accommodated.

One example is how to handle XML attributes as opposed to elements.  There really is no logical equivalent in JSON so how should attributes be included?  One option would be to ignore them, another might be to just include them in the JSON. 

There is also a question of structure.  For example in XML you could have:

<MyData>
  <name>Mike</name>
  <address>123 main</address>
  <name>Fred Flintsone</name>
  <address>Bedrock</address>
</MyData>

In XML you can have multiple tags of the same name in the same element (think HTML which is based on XML).  You cannot have multiple elements of the same name in JSON; you can have an array but you would lose the element order.

So basically, we are looking at what we could provide, however not all XML constructs can be mapped to JSON,

We don't tend to use audiodev.dll in the Get File Box logic.  That DLL is part of the Windows services that handle your audio driver.

It should be mentioned though that a quick search on the Internet turns up a warning that some viruses use this DLL name to disguise themselves.

https://www.file.net/process/audiodev.dll.html

You may want to check your system for viruses.

Frank,

You don't really need to track the index yourself simply use TCB(18) as in:

  def fn_find(local _array${all},pattern$)
  _array${all}=tbl(_array${all} like pattern$,_array${all},err=*next)
  if tcb(2) \
   then return dim(read min(_array$))+tcb(18) \
   else return dim(read min(_array$))-1
  end def
 !
  dim arr$[*]
  arr$[*]="alpha";
  arr$[*]="beta"
  arr$[*]="gamma";
  arr$[*]="delta"
 !
  idx=fn_find(arr${all},"^.am.a$")
  if idx \
   then print msg(="Entry that matches ""%3"" at index %1: %2",str(idx),arr$[idx],pattern$)

Here is a way to avoid using a FOR although it does use a bit more memory


  def fn_find(local _arrayname$, local TEXT$)
  local all$=sep+rec(cpl("IOLIST "+_arrayname$+"[ALL]"))
  return pos(sep=all$(1,pos(TEXT$=all$)),1,0)
  end def
 !
  dim x$[1:3]
  x$[1]="Cute kitten"
  x$[2]="Playful Puppy"
  x$[3]="Noisy Bird"
 !
  print fn_find("x$","Puppy")
The fn_find() function takes the name of the array (as a string -- not the actual array) and the text to find.  It then stuffs all elements in the array into a temporary string and scans it.

The ProvideX key enables the original ProvideX functionality, whereas the PxPlus key enables the PxPlus enhancements.

The use of two keys dates back to when we split off from Sage in 2005 and founded PxPlus.  While we have considered moving to a single key, we still have a number of clients using older unsupported products that require the old style keys.  Many companies buy new licenses then install old, sometimes unsupported, versions of PxPlus.