> (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.
Not sure about this one, b/c I'm not very experenced with Access, but writing an install program with VS.NET that would register the assembly in the GAC is not very difficult. This would allow you to distribute a install file that could be run on the client boxes via logon script or something like that (not sure if you have logon scripts on your network). > (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? > For this one, I'm not sure your scenario would give you the results you are expecting... I would create a client side class library that interacts with the remoting component, and let the CCW interact with the class library. I think that would provide you a simpler solution in the long run... Don
