Charlotte Foust
cfoust at infostatsystems.com
Wed Jul 23 12:35:53 CDT 2003
Nope, sorry, but that didn't work for me in Access 2002. I found that a long time ago, but it did not result in either a fixed reference or a compiled application, although the reference "thought" it was fixed. I had to work my way through to something that would work reliably and permanently when a customer opened the application using a runtime installation. Charlotte Foust -----Original Message----- From: Marcus, Scott (GEAE, Contractor) [mailto:scott.marcus at ae.ge.com] Sent: Wednesday, July 23, 2003 9:00 AM To: 'Access Developers discussion and problem solving' Subject: RE: [AccessD] Broken References in Runtime AXP Charlotte, I know that I'm jumping in the middle here but... Your solution is in the Microsoft knowledge base. The article is 194374. I have used this method for years. It works very well Here is a link to the article: http://support.microsoft.com/default.aspx?scid=kb;en-us;194374 Scott -----Original Message----- From: Charlotte Foust [mailto:cfoust at infostatsystems.com] Sent: Wednesday, July 23, 2003 12:01 PM To: Access Developers discussion and problem solving Subject: RE: [AccessD] Broken References in Runtime AXP OK, here's the situation as it stands. Using a query, as Gustav suggested, seems to give me an accurate way to test for a broken reference. I call that test from my FixReference routine and if it's true, I repair the library reference by removing it add adding it back. RefLibPaths gives me the correct path for adding it back, so that part is easy. This works in runtime or full installation and only performs the fix if the reference is actually broken. The compile issue is a bit trickier and I found a kludge, but I'm open to suggestions if anyone has them. The undocumented SysCmd(504, 16483) doesn't error but it doesn't seem to compile either. I ran into a post on the net that suggested it might not work with modules open (didn't say how you ran code otherwise, but I assume the reference was to the 97 VBE) so I started thinking "macro". If found that if I modify my autoexec macro, it will run the compile for me. So an autoexec that looks like this compiles the app after fixing the reference: Condition Action Command IIf(FixReference()=True,True,False) ... RunCommand CompileAndSaveAllModules OpenForm frmSplash 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