Now that I seem to be going okay with LINQ (at the moment), I've gotten myself into another interesting situation. I'm currently experimenting with a couple of sets of code in VB.NET (Express Edition, at the moment, but eventually to go to Pro), in which I'm collecting directory information in a VB form, then passing that to a VB .dll to query the XMLs in those directories and pass the results back to the form, meanwhile keeping information loaded in the .dll's memory for future use.

All fine and good, except that when I call the .dll's function name, I get an error message indicating that it can't find the entry point. I've checked the .dll under the Object Browser, and the functions seem to be quite visible, so I'm not sure what the problem is. I've added the .dll to my Resources and declared the functions, so VB knows everything is there.

Any ideas?

David M. Stowell

Could you post the problematic line of code?

Well, I've gotten around the problem, though we'll see what happens in the long term. I was trying to declare the .dll using the DECLARE statement, then simply using the function name later on, like this:

Declare Add Lib "MathLib.dll" (ByVal op1 As Decimal, ByVal op2 As Decimal) As Decimal

Dim lnSum As Decimal

lnSum = Add(3, 5)

It would blow up on the call to Add. Now I'm instantiating an object based on the .dll and that works. I'm just hoping that that works in the final environment - eventually the real .dll is going to be used in a Visual Foxpro application, which isn't .NET-aware. - it's COM. I know I can use CREATEOBJECT() in that code, but I hope that the two environments don't clash.

David