We sometimes experience a similar situation to this when performing any list based tool with maybe 30 functions or more. The local computer behaves as if Windows thinks Proiv has timed out, but if we wait long enough the Proiv process finishes and Window is happy again.
INSERT INTO #TEMP(COL1, COL2) VALUES('a','b') ENDSQL
(at least I get no errors!) but when I try to select and then subsequently read the selected entries by inserting
SELECT COL1, COL2 FROM #TEMP before the ENDSQL I get no records returned into the @F which corresponds to the file
Any suggestions please?
Is your SELECT statement in the same SQL DYNAMIC block as the CREATE and INSERT statements? Try having the SELECT statement in a seperate SQL DYNAMIC -> ENDSQL block. Also, make sure your SELECT statement is in the appropriate Logic point/location depending on the type of function you are programming in.
Is anyone using this and knows how it is supposed to work or can point me at where it's documented?
We currently use this file type to check if a file exists in a specified directory. I was also able to create a little recursive global update which searches a folder and all sub-folders within the defined folder for a specific file name, returning the path of the first file that matches.