I have just "released" an updated version of COMView, which is (besides other things) able to create ASM include files from type libraries. That may be useful for people working with COM, VB, ADO. Let me know what you think of it.
Click here to download
japheth
Click here to download
japheth
Very, very nice, and much appreciated.
I get a GPF if I try to create an inc file on any interface function with more than 32 parameters. (Like Access's Application_Run function.)
Other than that seems as smooth as silk.
I get a GPF if I try to create an inc file on any interface function with more than 32 parameters. (Like Access's Application_Run function.)
Other than that seems as smooth as silk.
Oops!! Seems like I counted some toes twice. There are only 31 parameters in the Access8 _Application Run function.
???
???
My last post on this ... I promise.
I think the issue is with the length of szStr in the ScanTypeInfoFunctions proc. The 'Run' function will generate a string approx. 400 bytes.
Is there any significance to the 260 byte length?
BTW: what version of windows.inc do you use? I'm having trouble building this project.
I think the issue is with the length of szStr in the ScanTypeInfoFunctions proc. The 'Run' function will generate a string approx. 400 bytes.
Is there any significance to the 260 byte length?
BTW: what version of windows.inc do you use? I'm having trouble building this project.
Thanks Wayne for reporting bugs.
260 is the value for MAXPATH, thats all.
About the windows.inc: I have made few "small" changes to windows.inc, thats true (completely forgotten about that). What can make problems are lines:
so the debugger is able to show me the strings.
Here is a small ADO sample showing how to use the gererated includes. The include ADODB.INC was generated with COMView. An access database is included. This app is 4 kB only. To run you need ADO and "OLE DB Provider for Jet engine" installed (should be the case if you have MS Access installed).
japheth
260 is the value for MAXPATH, thats all.
About the windows.inc: I have made few "small" changes to windows.inc, thats true (completely forgotten about that). What can make problems are lines:
LPSTR TYPEDEF DWORD
LPCSTR TYPEDEF DWORD
I have changed this to:
LPSTR TYPEDEF PTR BYTE
LPCSTR TYPEDEF PTR BYTE
so the debugger is able to show me the strings.
Here is a small ADO sample showing how to use the gererated includes. The include ADODB.INC was generated with COMView. An access database is included. This app is 4 kB only. To run you need ADO and "OLE DB Provider for Jet engine" installed (should be the case if you have MS Access installed).
japheth
@Japheth:
Really, reallly, really nice work! :alright:
Really, reallly, really nice work! :alright:
Dear japheth,
Your tool is so very nice to me
(meaning both functionality and how it is coded) ;-)
Thanks.
Your tool is so very nice to me
(meaning both functionality and how it is coded) ;-)
Thanks.
Thanks for the replies, guys!
The error reported from Wayne (incl. analysis! thanks again) is fixed, the parameter line can reach up to 512 bytes now (if I remember correctly, this is maximum for MASM "logical" lines). So hopefully MS doesn't design methods with 100 parameters.
The error reported from Wayne (incl. analysis! thanks again) is fixed, the parameter line can reach up to 512 bytes now (if I remember correctly, this is maximum for MASM "logical" lines). So hopefully MS doesn't design methods with 100 parameters.
japheth,
Thanks for windows.inc changes. Project builds fine now.
Thanks for the ado example also. I'll check it out tonight.
(Only have Accessc97 on this machine)
Thanks for windows.inc changes. Project builds fine now.
Thanks for the ado example also. I'll check it out tonight.
(Only have Accessc97 on this machine)