It's not a CVAL. I'm using a Delphi DLL 97k in size that does a bunch of FileInfo stuff, amongst which is the FileVersion information.
These requirements are part and parcel the rationale behind being able to have your own library. You can Declare up to 200 functions (RBase mapping to the function in memory) of either custom DLLs or a Substantial number of WinAPI functions that have datatypes compatible with RBase. If your concern is distribution, I would house them in VARBIT in the DB. Once excised from the DB, place them anywhere in the Windows default search path and no specific mapping is required in the DLCall function, but if the DLL is in a non-searched path, then the FullPathName of the DLL must be included in the DLCall function. I can send you the file with the RMD and in a couple days the helpfile will be in the wild for everyone. ----- Original Message ----- From: "Lawrence Lustig" <[EMAIL PROTECTED]> To: "RBASE-L Mailing List" <[email protected]> Sent: Tuesday, June 24, 2008 3:57 PM Subject: [RBASE-L] - RE: Compiler -- getting underlying engine version. > << > The EXE version information can be extracted as can the RBENGINE76.DLL > version > > information. > > For example on my desktop the RBG76.exe is reported as 7:06:34.623 while > RBENGINE76.DLL is reported as 7:06:33.609 >>> > > What is the CVAL argument to extract the build information from the > RBENGINE76.DLL from inside a compiled executable? I can't find it. I get > back 0.0.0.0 (or, presumably, whatever version info I set before compiling). > -- > Larry
