Post by billgrantford on May 18, 2021 16:46:35 GMT 1
ARAGO creates local files ...NDX DBF and so on to run local. Once the editing of the files is completed the edited data is sent back to the server. When doing a search in the database (DBF) a INDEX (NDX) is created however only the TEMP.NDX is created then vDos started task goes dead. the folders are C:\INVOICE and C:\INVOICE\INVOICE I've checked permissions on related folders all access is given still the only files being generated is the index that stalled at 1k.
Complete correction to the above Post:
To sum this up since there was a break in testing. When searching a name against a database, the search stalls and does not complete.
What appears to happening is the search on the database file, which is large, the search stalls out. This test was conducted with "QUICKIDLE=OFF" , I've tested this in various forms on the name search. Example by last name, full name the results are the same as to stall and not complete.
Everything else functions excellent, this our last hurdle to implement vDOS...
Post by billgrantford on May 20, 2021 17:43:12 GMT 1
So our software ARAGO creates TEMP files for the DBF's it uses. All editing is done on the local machine, when we complete the editing the data is then transferred back to the database that resides on the servers. I have observed this activity, but not all the required TEMP files are being generated on the local machine. Also I see that almost all the temp files are deleted when the task is completed, I'm not sure that this is an issue. Files like PRTTEMP are not generated and lock the main PARTPRINT.DBF, I'm assuming by these actions VDos is locking the file, which it should generate a PRTTEMP work file on the local machine. All this being said the time to response is extremely slow to a non-responsive state. How does vDos handle temp files?
Post by billgrantford on May 28, 2021 15:36:33 GMT 1
Update...the last application executable with an issue. GOTCK.EXE which access our INVOICE Database through various menu options, fails when searching the database by customer name. The Database name is PRTPRINT at 70,500 kb, the local index file is created, the PRTPRINT is locked during the search. While watching my local Task Manager the vDOS task is working away then falls off to idle state. I will say that once in a while the search does complete retuning the results, however 99% of the time the task has to be ended via Task Manager. I have ran down the security route and that is fine....I've ran down the resource allocation route to a dead end. What do you think?