Rob,
   Just to let you know there are typo's in the path for the
Magine.config file, and the reg file. You will find that the % sign is
in the wrong place for the path, and more importantly what affecting you
problem is that the reg file has the PublicToken does not match the
assembly token. So navigate to the window's directory, then to the
assembly folder. Now find the FirebirdSql.Data.FirebirdClient and right
click and select properties. There you can highlight and copy the
correct public key for the assembly. You now need to replace the public
key in the reg file and reregister the provider. You can also navigate
to the registry entry and replace it if you would prefer.

Thanks,

Steven

1. The path is not correct in that file 
>Not much help on your problem, except that I have the identical setup
>and it works just fine.
>
>Make sure the registry paths point to where the firebird client
>software really is.
>
>Marv
>
>On 6/17/07, Planet <[EMAIL PROTECTED]> wrote:
>>
>>
>>
>> Hello,
>>
>>
>> I've installed Firebird Client 2.1.0-RC1 and the DEX provider 2.0.2
and >>the
>> FirebirdDDEXProviderPacakgeLess32.reg file.
>> I've added the entries to the machine.cfg file.
>> I'm using VS2005 Professional with SP1 on Vista Business.
>>
>>
>> The components are visible in the toolbox after activating them, so
far >>so
>>good.

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Firebird-net-provider mailing list
Firebird-net-provider@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/firebird-net-provider

Reply via email to