Stuart McLachlan
stuart at lexacorp.com.pg
Fri Mar 12 19:26:07 CST 2004
But not the same set of installed software/OS version to the system where the database was developed. There willl be a reference to something (such as a specific MDAC version) that was on the development machine but not on the HP. On 12 Mar 2004 at 19:29, John Eget wrote: > it is the exact same database on each pc > > > ----- Original Message ----- > From: "MartyConnelly" <martyconnelly at shaw.ca> > To: "Access Developers discussion and problem solving" > <accessd at databaseadvisors.com> > Sent: Thursday, March 11, 2004 8:09 PM > Subject: Re: [AccessD] date on HP PCs > > > > Probably a missing reference. On the HP's open up the mdb modules > > Tools--> Reference and check for the flagged missing ones. > > You may have something like a specific reference pointer to ADO MDAC 2.5 > > and say you are using WinXP( it will only have ADO 2.7 by default.) > > > > > > > > John Eget wrote: > > > > >I had the oddest thing happen today, My databases do not show =Date(), > but only on the new HPs in work. > > >Has anyone come across this before? > > >John > > > > > > > > > > -- > > Marty Connelly > > Victoria, B.C. > > Canada > > > > > > > > -- > > _______________________________________________ > > AccessD mailing list > > AccessD at databaseadvisors.com > > http://databaseadvisors.com/mailman/listinfo/accessd > > Website: http://www.databaseadvisors.com > > > -- > _______________________________________________ > AccessD mailing list > AccessD at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/accessd > Website: http://www.databaseadvisors.com -- Lexacorp Ltd http://www.lexacorp.com.pg Information Technology Consultancy, Software Development,System Support.