Hi, We used to deploy midas.dll separately in each client machine until after reading a similar article mentioned by Traci and yes, we got rid of this problem by simply adding "midaslib" to the project's "uses" clause. We are using Delphi 7.
Btw, I've just joined the group lately. Am from Fiji and unfortunately we dont have a Delphi Users Group here. I only know of 3 others here who program in Delphi and they (including me) all work for the same company. Hoping that i'm welcomed here :) With best regards, Alfredo Ferrer Senior Analyst Programmer Land Transport Authority of Fiji <http://www.ltafiji.com> Valelevu, Fiji Islands email: [EMAIL PROTECTED] , [EMAIL PROTECTED] On 10/3/07, Rohit Gupta <[EMAIL PROTECTED]> wrote: > > Well, thats too neat a trick to achieve. It appears that everyone is now > placing their dlls in the same folder as their exes. > > Stacey Verner wrote: > > > > I don't think you should expect midas.dll to be present on a clients > > machine. > > > > It's a Borland dll and would only be present if they already have a > > midas (DataSnap) based application installed. > > > > Your installer should install it, but not overwrite a newer version. > > > > Stacey > > > > _______________________________________________ > NZ Borland Developers Group - Delphi mailing list > Post: [email protected] > Admin: http://delphi.org.nz/mailman/listinfo/delphi > Unsubscribe: send an email to [EMAIL PROTECTED] with Subject: > unsubscribe >
_______________________________________________ NZ Borland Developers Group - Delphi mailing list Post: [email protected] Admin: http://delphi.org.nz/mailman/listinfo/delphi Unsubscribe: send an email to [EMAIL PROTECTED] with Subject: unsubscribe
