It never (i.e. never) makes sense to have a varM in a fact variable, because that is completely equivalent to having the value directly in the fact variable, except that it becomes more complex. Yes, I was getting carried away trying to apply these new routines. (I find it strange that you mix valu...

I'm probably getting carried away now but am looking at applications of the collection library in my code and another question has arisen. The following is a simplified example for the purposes of my question. The predicate "collect_data" creates a column of report data subtotalling by DEP...

That makes good sense.

Cheers,

David

Thank you Thomas. I'm starting to get a feel for collections now and followed the "keyword recognition" and "text concordance" examples. Just 1 more question regarding collections; if lists and internal databases are collections then it seems that the collections library is anoth...

Thank you Thomas and Peter. The following is simple and clean: LNAMES = [Name || CODE in SLCODES, nameRefDB(CODE, LabelCODE), get_label(LabelCODE, Name)] Having read a little further on this now I'm starting to get a feel for using varM and collections. I have a feeling I could use collections a gre...

This is a general question concerning code usage and style. Given: A list of reference numbers - SLCODES An internal database - nameRefDB A temp working internal database - labelDB Predicate to find the relation to each number - get_lable is there a difference in the following coding methods to obta...

I haven't actually been editing forms or dialogs for awhile so had a quick look just now. As you suggested I disabled the AV I'm currently using (Avast) but find it can still happen. In actuality it shouldn't happen in normal practice though. I discovered by random test that if you open a dialog, se...

Ah now I get it!

I didn't read the description carefully and wasn't looking at the parameter in Thank you Thomas.

Hi Thomas, Thank you but I'm getting quite confused. As far as I can tell the following will catch any and all reasons a file cannot be created or opened if D = exception::tryGetDescriptor(TraceId, fileSystem_api::cannotCreate) then... What I need to do is determine whether the file does not yet exi...

My description of the problem was somewhat indirect here but the exception routines to get the error code in the "try...catch" routine does not return the correct error at least with the "openfile" function. I apologise if the issue is being looked at but as there was no response...

I created a small example project which demonstrates the problem.

Best wishes for the New Year!

Cheers,

David

It came to mind that I could test the above by simply sending error code 2 (file not found) to the error handler in the event an exception is raised as in the following: displayPrint(WIN,PAGE) =Y:- retractFactDb(preview_update), try inStream := inputStream_file::openFile8(re_temp_file_name) catch _T...

Hi Thomas, It turns out there is a change in either the "try...catch" predicate or in the "exception" predicates. In VP 7.4 the openfile routine causes an exception since the file has not yet been created. It's caught by the "try...catch" and getLastError produces error...

Hi Harrison, I remember when I upgraded this particular module from VP 5.2 to VP 7 there was a timing issue as you suggested although I didn't think there would be any significant performance/timing issues between VP 7.4 and VP 7.5 (and it works in 7.4). I've tried some simple timing changes and so ...

I have another issue which seems to be related to VP 7.5 (I notice in the dump message "definiteUserError = true" and I suspect there may be something simple here). The code where the error occurs is as follows: displayPrint(WIN,PAGE) =Y:- retractFactDb(preview_update), try inStream := inp...