If a dll is slightly different. Say not as upto date as the one from which the application was design in. How do you sort the problem. I've spent a few hours a day this week trying to figure it out and search here and elsewhere but either I am missing something or I'm very very dense.
Sorry I'm gettin confussed. They didn't leave enough active brain in my head. Right to clarify. I have an application that was writen in access 2.0 and running on about 5 machines. The client wanted it updated to run in 2002 then packaged up and distributed back to the machines that still have Access 2.0. So now these machines will still be able to run their other Access 2.0 application in Access 2.0 but also use the 2002 version of said application with a run time licence in 2002. However there is a dll conflict that I need to resolve (I think) However with the 2002 version being run time I can't look in to Tool> References to check whats adrift.
So if I find there is a dll thats out of date I'm guessing it may cause errors in the Version 2.0 apps. Should the packagin wizard instal with the run time version of 2002 the right dll's?
Make any sense? Damn shagged out body and brain aint what it used to be...
