Solution:

In the past, the problem with resource loss under VisiDAQ is very difficult to "feel", that means we could know this problem after a long time, maybe several hours or a couple of days, then find out the performance of system is very poor or hard disk is always working hard. Actually, VisiDAQ has removed such a problem, but some strange phenomenons could be misunderstood as resource problem. In order to distinguish this problem, you can use system.freeresources and system.freememory commands under VisiDAQ to check it. The following is for your information: ====================== Sub SCR1( ) dim resource_available as integer dim memory_available as long resource_available=system.freeresources memory_available=system.freememory outputi 0,resource_available outputl 1,memory_available End Sub ====================== If you want to know the detail, please refer to Help under Basic Script. Note: system.freememory is useless under Win95 because the value will not change any more, but it can work well under Win3.1.