Erwin Craps
Erwin.Craps at ithelps.be
Mon Jul 21 13:49:58 CDT 2003
Haha, I had some same probs last week... I converted some A2K apps (that I use in mde format) to XP and found to that I had some broken refenrences. That I concluded because simple date() function did not worked in the mde file. However, when I checked my MDB all refenrences where correct and the MDB was fully functional!!!. I solved the issue by decompiling (/DECOMPILE) the MDB file and then generate the MDE file. Problem solved!!! Erwin -----Oorspronkelijk bericht----- Van: Charlotte Foust [mailto:cfoust at infostatsystems.com] Verzonden: maandag 21 juli 2003 17:33 Aan: Access Developers discussion and problem solving Onderwerp: RE: [AccessD] Broken References in Runtime AXP Actually, I did all those things already, including creating the RefLibPaths key for my library. *However*, I followed the MSKB article and used the complete path, including the filename in the data for the key. When I removed the filename and just kept the path, it worked. Is there a reason for the double backslashes in the path in data? It appears to work on my machine without them, but I'm dealing with a local drive, not a mapped drive or UNC path. Charlotte Foust -----Original Message----- From: Shamil Salakhetdinov [mailto:shamil at smsconsulting.spb.ru] Sent: Friday, July 18, 2003 11:27 PM To: Access Developers discussion and problem solving Subject: Re: [AccessD] Broken References in Runtime AXP Charlotte, I created a topic on my web site to test RefLibPaths with MS Access XP (without custom profiles) - please have a look - http://smsconsulting.spb.ru/shamil_s/topics/testrefs.htm - does it answer your question? HTH, Shamil ----- Original Message ----- From: "Charlotte Foust" <cfoust at infostatsystems.com> To: "Access Developers discussion and problem solving" <accessd at databaseadvisors.com> Sent: Friday, July 18, 2003 9:47 PM Subject: RE: [AccessD] Broken References in Runtime AXP > Well, I put RefLibPaths on my machine, but when I open the application > from a full version of Access, I still get a broken reference. Is > there something else I have to do to kick Access in the pants and make > it actually use RefLibPaths to resolve the reference? > > Charlotte Foust > > -----Original Message----- > From: Shamil Salakhetdinov [mailto:shamil at smsconsulting.spb.ru] > Sent: Friday, July 18, 2003 9:33 AM > To: Access Developers discussion and problem solving > Subject: Re: [AccessD] Broken References in Runtime AXP > > > > I'm a bit wary of relying on it. > Charlotte, > > It works well in 100% of cases - guaranteed - it was tested and used > with several MS Access97 runtime/programs installations having several > (sometimes > 30+) library databases (together with SageKey for InstallShield5.1 > 30+patched > script and when manual (batch file) installations were used with > preinstalled MS Access) on different environments , MS Windows > versions, MS Windows/Office national versions... > > The only problem is to properly use RefLibPaths as it's described in > online help - I've been in the same situation like you're now (I mean > your "banging your head against brickwall") - it wll take some time > until you'll get comfortable with RefLibPaths and maybe custom > profiles > - I'd recommend to use them too... > > Shamil > > ----- Original Message ----- > From: "Charlotte Foust" <cfoust at infostatsystems.com> > To: "Access Developers discussion and problem solving" > <accessd at databaseadvisors.com> > Sent: Friday, July 18, 2003 7:22 PM > Subject: RE: [AccessD] Broken References in Runtime AXP > > > > Shamil, > > > > I wasn't ignoring your suggestion but I agree that the help article > > is > > > not accurate. In fact we started out putting the code library in > > the same folder with the application. Guess what? When the app was > > installed in a different folder from the one the setup was created > > from, Access found the file and did not report a broken reference > > but strange things happened that were only cured by unchecking and > > resetting the reference. > > > > I've played with RefLibPaths but I did not see it resolve any > > references automatically, at least not when I broke one > > deliberately, so I'm a bit wary of relying on it. The search for > > solutions continues ... > > > > Charlotte Foust > > > > -----Original Message----- > > From: Shamil Salakhetdinov [mailto:shamil at smsconsulting.spb.ru] > > Sent: Thursday, July 17, 2003 7:28 PM > > To: Access Developers discussion and problem solving > > Subject: Re: [AccessD] Broken References in Runtime AXP > > > > > > > I'm just going off to sit in the corner and gibber. > > Charlotte, > > > > I'm sorry I don't particiapte actively in this thread - please > > reread very carefully this paragrapgh of MS Access online help: > > > > <<<<<<<< > > d.. If you set a reference to a project or type library from > > Microsoft Access and then move the file that contains that project > > or type library to a different folder, Microsoft Access will attempt > > to locate the file and reestablish the reference. If the RefLibPaths > > key exists in the registry, Microsoft Access will first search > > there. If there's no matching entry, Microsoft Access will search > > for the file first in the current folder, then in all the folders on > > the drive. You > > > can create the RefLibPaths key by using the Registry Editor in > > Windows, under the registry key > > \HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\version\Access. For > > more > > > information about using the Registry Editor, see your Windows > > documentation. > > >>>>>>>> > > I think this is the key sentence "Microsoft Access will search for > > the > > > file first in the current folder, then in all the folders on the > > drive." > > - I mean that MS Access will search first in the CURRENT folder, > > then > in > > ALL the folders on the drive. I don't think it's 100% accurate - if > > MS Access have been searching in ALL the folders on the drive for a > broken > > reference then it would have worked ages to resolve such refs on MS > > Access program start-up. So I think it searches first in the current > > folder and then starting from the current folder in all the > > subfolders and probably in all the parent folders of the current > > folder and their subfolders and then (of before?) in all the folders > > listed in PATH environment variable. This extra-intelligence of MS > > Access sometimes drives developers crazy... > > > > Solution, which I used was to develop MS Access projects on > > different drive(s)/under different paths than deployment > > drive/directory and NEVER put referenced MS Access databases in the > > directories from PATH environment variable. > > > > I've also used RefLibPaths separatley and with SageKey scripts to > > install > > runtime(Access97) and its environment. Please reread again the > > sentence above - when RefLibPaths is used then MS Access FIRST > > searches for broken references in the directoriy from RefLibpaths... > > > > But if the reference ISN'T broken then even if RefLibPaths is > > specified MS Access DOESN'T use its value for resolve a reference on > > runtime - I think this is contr-intuitive and this is why is good to > > force the refs being broken by having your development > > drive/directory > > > different from deployment ones... > > > > Why you can't use RefLibPaths with your rutime environment? > > > > Shamil > > > > > > > > ----- Original Message ----- > > From: "Charlotte Foust" <cfoust at infostatsystems.com> > > To: "Access Developers discussion and problem solving" > > <accessd at databaseadvisors.com> > > Sent: Friday, July 18, 2003 4:38 AM > > Subject: RE: [AccessD] Broken References in Runtime AXP > > > > > > > Well, I'm now officially round the bend. I just sat here and kept > > > seeing the idiot thing report that it found the broken reference > > > in the right location, which is where the file *is* but not where > > > the reference actually pointed. The FullPath property of the > > > reference returned the right location instead of the broken one! > > > Then I watched > > > > > the referenced library pop up in the project explorer even though > > > it > > > > wasn't there when I opened the project! I'm just going off to sit > > > in the corner and gibber. > > > > > > I'm running Windows XP and I wonder if that has anything to do > > > with it. I've also seen it report a broken reference and say it > > > fixed it in > > > > > runtime and have the app appear to run OK but then when I opened > > > it normally and held down the shift key, the reference was broken. > > > Usually if it's broken it stays broken ... But not always! > > > Aaarrrgggghhhh!!! > > > > > > Charlotte Foust _______________________________________________ > > > 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 > _______________________________________________ > 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