Jim DeMarco
Jdemarco at hudsonhealthplan.org
Tue Mar 2 10:03:26 CST 2004
Well we took it out and recompiled and we're good to go! Thanks to all, Jim D. -----Original Message----- From: Rocky Smolin - Beach Access Software [mailto:bchacc at san.rr.com] Sent: Tuesday, March 02, 2004 10:39 AM To: Access Developers discussion and problem solving Subject: Re: [AccessD] A2K MDE Runtime Reference problem - URGENT Jim: I've had extra references creep into my apps and I don't know where they came from. So now, from time to time, if I can remember, I check the references at random to see what's there. Rocky ----- Original Message ----- From: "Jim DeMarco" <Jdemarco at hudsonhealthplan.org> To: "Access Developers discussion and problem solving" <accessd at databaseadvisors.com> Sent: Tuesday, March 02, 2004 7:01 AM Subject: RE: [AccessD] A2K MDE Runtime Reference problem - URGENT > Rocky, > > They don't have the correct version of Access installed (at the win98 location). I found what I think is the offending reference (to a file named cnfgprt.ocx). We're going to remove it then recompile the app and see if it runs. I think that ocx is some NT service pack file but why it's referenced here is a mystery. > > Jim DeMarco > > -----Original Message----- > From: Rocky Smolin - Beach Access Software [mailto:bchacc at san.rr.com] > Sent: Monday, March 01, 2004 1:28 PM > To: Access Developers discussion and problem solving > Subject: Re: [AccessD] A2K MDE Runtime Reference problem - URGENT > > > Jim: > > If they can load Access on that machine, you could send them a stripped down > version of the app as an mdb and it should blow dumping them into the code > window. From there you could walk them through displaying the references to > see which one is broken and the do a search on it, copying it to the > expected directory. > > Rocky > > ----- Original Message ----- > From: "Gustav Brock" <gustav at cactus.dk> > To: "Access Developers discussion and problem solving" > <accessd at databaseadvisors.com> > Sent: Monday, March 01, 2004 9:36 AM > Subject: Re: [AccessD] A2K MDE Runtime Reference problem - URGENT > > > > Hi Jim > > > > > Yes I did. I'll check to see if they did. I just did a win98 > > > install got the #name? error which is good in that at least I've got > > > a platform to test against. > > > > I forgot, at Win 98 it can't be an admin rights' issue. > > > > Then it's probably because a reference exists on Win 98 but of a lower > > version than that on your development machine. Access is not very keen > > to accept a lower version of a reference. > > Either install the newer version of the reference on Win 98 or compile > > your app with the lower version of the reference. > > > > /gustav > > > > > > > Maybe your client installed it without Administrator rights - which > > > you probably did? > > > > > /gustav > > > > > > >> I just installed on an XP system here and the app worked. Some > read-only issues that I believe relate to security on the machine I was on > but the date functions all worked. > > > > >> I seem to recall some code in the archives that set references. I'll > take a look there and see what comes up. > > > > >> Thanks again, > > > > >> Jim D. > > > > >> -----Original Message----- > > >> From: Gustav Brock [mailto:gustav at cactus.dk] > > >> Sent: Monday, March 01, 2004 9:32 AM > > >> To: Access Developers discussion and problem solving > > >> Subject: Re: [AccessD] A2K MDE Runtime Reference problem - URGENT > > > > > > >> Hi Jim > > > > >> The Date fields are the symptom only. > > >> The cure is to locate and reestablish one or more missing reference. > > > > >> Access will - and is quite good at it but not perfect - try to locate > > >> any missing reference in the current environment, thus adjusting the > > >> path for each of these references. > > >> Maybe Access succeeded when the MDE was moved to your platform > > >> (Win2000 and C:\WINNT) but failed when it moved "back" (Win 9x/XP and > > >> C:\Windows) at the clients. > > > > >> /gustav > > > > >>> The real mystery is that we have not changed or added any references. > It just seems the date fields that have the problem. > > > > -- > > _______________________________________________ > > 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 > -- > _______________________________________________ > 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