Calling C# programmers...

[zehd]

I have a C# programmed DLL ( for sqlite3 access ) that was converted for use with VB6. It works great, but I think the DLL is having pathing issues.

Specifically, instructions say that the dll must be copied to the Windows directory. I'm having no problems if the the windows is on C drive. I think my users are having trouble with other partitions...

This test application requires the SQLite3VB.dll (that can be created using this tutorial or found below) to be located in your computer's system folders (Ex C:\Windows)

The following page is a walkthrough for C# programmers that gives the source code for the DLL and shows what to do to compile a VB6 compatible DLL...

http://www.tannertech.net/sqlite3vb/index.htm

Can someone look at the source and confirm if there is a pathing issue, whether it could be tweaked to run from anywhere, like my app.path and not Windows, and whether THEY could compile the new DLL for me?


Thanks so much...

[whurlston]

That's C++, not C#. If it is in a system directory, there should not be any pathing issues unless the machine's environment variables are wrong, which would have other consequences as well. It's been a while since I used VB6 so I may be wrong on that though. You could try putting it in the System32 directory.

[Carlito]

I took a look through the source and couldn't find any hard references to windows directories..
and whurlston is correct, it's c++ not c#

[zehd]

Thanks a lot guys. Very helpful and speedy...

But then that's GB-PVR users for you...

[mvallevand]

If you still need help with this let me know, if I remember back through the cobwebs dll's in app.path aren't by default located because the real executable is the vb6 run time. You might need to change the default directory and drive if necessary to app.path to get app.path into the search path.

Martin

[zehd]

If you still need help with this let me know, if I remember back through the cobwebs dll's in app.path aren't by default located because the real executable is the vb6 run time. You might need to change the default directory and drive if necessary to app.path to get app.path into the search path.

Martin

Normally, I have that sorted. I don't know what is going on, because I have one program that references the dlll perfectly, and other causing trouble for others. I can't recreate it. And it turns out the guys have default C:\Windows setups anyway...

I started typing random code and hit 'compile'... I wonder if that will help...