Custom code, I trust the code impeccably.  It does work,  just if I try to use 
it more than once in a given command it fails after the second or third time I 
try to process it.  

 

>From the process you can tell I am getting file information and wanting to 
>cross check it with the file information that they should have.  Should it be 
>wrong I can then exit them out and start a separate routine to update them to 
>current file spec’s.  In an earlier process it checks the number of 
>occurrences and finds dups. I will perhaps incorporate a process to evaluate 
>the true and most recent file and apply that file and delete the one that 
>fails the test.

 

I want users at 30+ locations to be up-to-date and no orphan file(s) as I have 
found. This is run in an rff.

 

I believe between the set var 3 and 4 I might have to release the dll and 
reapply.  Not a problem – I think ;) ?     but that’s why I am asking.  I have 
tried several approaches, but sometimes I am blinded and cannot see beyond my 
desktop.  

 

 

Sincerely,

Paul D.

 

 

Example:

SET VAR varg ='FileN1'

SET VAR vaction = 'FileName'

IF (chkfunc('GetVerInfo')) = 0 THEN

  STDCALL function 'GetVerInfo' (ptr text (256) ,ptr text (128) ,ptr text 
(128)) : text

ENDIF

SET VAR vfilename3 = 'C:\WINDOWS\system32\RB76_32.DLL'

SET VAR vversion3 TEXT = (dlcall('dllName.dll', 'GetVerInfo', vfilename3, varg, 
vaction))

SET VAR vfilename4 = C:\WINDOWS\system32\RBENGINE76.DLL’

SET VAR vversion4 TEXT = (dlcall('dllName.dll', 'GetVerInfo', vfilename4, varg, 
vaction))

 

 

Ps   the dll was posted here a long time ago by Mike B. the reason I did not 
provide the dll code.  “I hope Mike does not mind me telling the RList that.”  

 

 

From: [email protected] [mailto:[email protected]] On Behalf Of Lawrence Lustig
Sent: Wednesday, December 02, 2009 12:09 PM
To: RBASE-L Mailing List
Subject: [RBASE-L] - Re: DLL call

 

<< 

I am attempting to get several files checked with a dll and display the 
results.  RBase process’s sometimes one or two command lines.  At least always 
one command line then it stops.  It is still running in the background but it 
will run hours.  Tried it in 7.6 latest and 9.0 

>> 

 

Could you post the code?

 

Are these custom DLLs?  If so, the problem is more likely to reside in the DLL 
itself.  Does the DLL provide a debugging mode that can show you whether it's 
been called and/or has returned, and what it's doing?

--

Larry

Reply via email to