S o S

[Harsha]

Hi,

I wrote a function for saving records in a table. And then I had compiled
that function into a dll. But when I tried calling that dll from my form,
I'm getting an error message.

Err. Description says 'Microsoft OLEDB Service Components' and the
err. no says 1000440.

Can you guys help me out,please?

Harsha

[Russ]

"Harsha" <Harsha@Techemail.Com> wrote:
>
>Hi,
>
>I wrote a function for saving records in a table. And then I had compiled
>that function into a dll. But when I tried calling that dll from my form,
>I'm getting an error message.
>
>Err. Description says 'Microsoft OLEDB Service Components' and the
>err. no says 1000440.
>
>Can you guys help me out,please?
>
>Harsha

Harsha,
You can debug your .dll code by doing the following:
* Open your .dll project
* Click File | Add Project and select Standard EXE.
* In the project explorer, right click on Project1 and
select "Set as Start Up from the context menu.
* In Project1, add a reference to your .dll under Project | References.
* Add a command button to Project1. You can use this button to call
your .dll to test it.

Now when you run the project, Project1 will start first. When you step through
the code, the debugger will step into your .dll code also, allowing you to
figure out where the problem is.

HTH,
-Russ.

[Harsha]

Thanks Russ. I'm going to do the things you suggested right away. But tell
me, should I install the dll that I write with the system registry? How do
I do that.

Thanks

Harsha

"Russ" <russell.thompson@adlink.com> wrote:
>
>"Harsha" <Harsha@Techemail.Com> wrote:
>>
>>Hi,
>>
>>I wrote a function for saving records in a table. And then I had compiled
>>that function into a dll. But when I tried calling that dll from my form,
>>I'm getting an error message.
>>
>>Err. Description says 'Microsoft OLEDB Service Components' and the
>>err. no says 1000440.
>>
>>Can you guys help me out,please?
>>
>>Harsha
>
>Harsha,
>You can debug your .dll code by doing the following:
> * Open your .dll project
> * Click File | Add Project and select Standard EXE.
> * In the project explorer, right click on Project1 and
> select "Set as Start Up from the context menu.
> * In Project1, add a reference to your .dll under Project | References.
> * Add a command button to Project1. You can use this button to call
> your .dll to test it.
>
>Now when you run the project, Project1 will start first. When you step
through
>the code, the debugger will step into your .dll code also, allowing you
to
>figure out where the problem is.
>
>HTH,
>-Russ.
>
>
>
>
>

[Russ]

"Harsha" <Harsha@Techemail.Com> wrote:
>
>Thanks Russ. I'm going to do the things you suggested right away. But tell
>me, should I install the dll that I write with the system registry? How
do
>I do that.
>
>Thanks
>
>Harsha
>

For debugging purposes, you don't even need a compiled .dll because the ide
will be able to find the code in your .dll project. You still need to set
a reference to it though. When it comes time to install it on a user's machine,
I believe ActiveX .dll's/.ocx's are self-registering, but you can register
it using RegSvr32.exe just to be sure.

-Russ.