Thanks, Naomi. Traci's situation much more complex than mine, but it did remind me to check Rick Strahl's stuff and that reminded me that if I compile the dll in .net I'm going to need .net runtimes on the boxes that run it and that will be fine for the SQL conversion as they'll have .NET installed with SQL.
If I ever get this things working I'll be sure to post the dll since there really is no good way to do this in VFP.
>>Trying to clarify my understanding :
>>
>>I have a function in VB .net (checks to see the current status of a printer) Receives a param of type string, returns an integer. I would like to create a DLL that I can call from VFP to get that integer after passing it the string.
>>
>>Do I just put the function in a module, compile it as a DLL, register it, and the do a oprinterchecker=creatobject('Printerchecker')
>>lnstatus=oprinterchecker.PrintStatus("\\server\LaserPrinter")
>>
>>or is there something else I need to be thinking about?
>>
>>TIA
>
>Looks like Tracy is on the same page as you
>
Accessing a C# .NET com interop dll from VFP Thread #
1324166 Message #
1324166
Charles Hankey
Though a good deal is too strange to be believed, nothing is too strange to have happened.
- Thomas Hardy
Half the harm that is done in this world is due to people who want to feel important. They don't mean to do harm-- but the harm does not interest them. Or they do not see it, or they justify it because they are absorbed in the endless struggle to think well of themselves.
-- T. S. Eliot
Democracy is two wolves and a sheep voting on what to have for lunch.
Liberty is a well-armed sheep contesting the vote.
- Ben Franklin
Pardon him, Theodotus. He is a barbarian, and thinks that the customs of his tribe and island are the laws of nature.
