I posted this to the .NET-CLR list about 5 days ago but no one has
responded ...

Our shop is still in the stone age technologically, using Access (often
Access 97) in combination with SQL Server for many projects. I am trying to
get our group to move to .NET, skipping over COM. To that end, I have been
able to reference and call a simple .NET object from Access 97 by creating
a type library, registering the assembly and placing it in the global
(1) However, placement in the global cache requires strong name creation
which would be a hassle to do on our various Access 97/2000 client
machines. I have been unable to figure out how to simply use a private
assembly for this purpose. Placing it in either WinNT\System32 or in the
Access.exe directory fails to get Access to list the assembly in
its "Reference" object list.
***
(2) Furthermore, what I really wish to do is to allow Access 97/2000
clients to call .NET components residing on a separate box (my gosh, a
pursue, and if so, would I simply wrap the .NET remoting stub in a COM
callable wrapper and call that wrapper from Access?

Thanks for any help!

Reply via email to