<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE>Message</TITLE>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.2719.2200" name=GENERATOR></HEAD>
<BODY>
<DIV><SPAN class=017471619-23072003><FONT color=#0000ff
size=2>Jim,</FONT></SPAN></DIV>
<DIV><SPAN class=017471619-23072003><FONT color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=017471619-23072003><FONT color=#0000ff size=2>I agree with
you. Especially since this topic has involved some of the best minds on
the list and has dragged out for several days now, a good write-up of the
problem and its solution will be looked forward to by many of us. And
submitting the write-up as an article to Many-To-Many will give you an extra
item to add to the resume.</FONT></SPAN></DIV>
<DIV> </DIV><!-- Converted from text/rtf format -->
<P><SPAN lang=en-us><B><FONT color=#0000ff>Charles Wortz</FONT></B></SPAN>
<BR><SPAN lang=en-us><FONT color=#0000ff>Software Development
Division</FONT></SPAN> <BR><SPAN lang=en-us><FONT color=#0000ff>Texas Education
Agency</FONT></SPAN> <BR><SPAN lang=en-us><FONT color=#0000ff>1701 N. Congress
Ave</FONT></SPAN> <BR><SPAN lang=en-us><FONT color=#0000ff>Austin, TX
78701-1494</FONT></SPAN> <BR><SPAN lang=en-us><FONT
color=#0000ff>512-463-9493</FONT></SPAN> <BR><SPAN lang=en-us><FONT
color=#0000ff>CWortz@tea.state.tx.us</FONT></SPAN> </P>
<DIV></DIV>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left><FONT face=Tahoma
size=2>-----Original Message-----<BR><B>From:</B> Hale, Jim
[mailto:jim.hale@fleetpride.com] <BR><B>Sent:</B> Wednesday 2003 Jul 23
14:09<BR><B>To:</B> 'Access Developers discussion and problem
solving'<BR><B>Subject:</B> RE: [AccessD] Broken References in Runtime
AXP<BR><BR></FONT></DIV>
<P><FONT size=2>The final solution would make a great article (he suggested
beggingly)</FONT> <BR><FONT size=2>Jim Hale</FONT> </P>
<P><FONT size=2>-----Original Message-----</FONT> <BR><FONT size=2>From:
Charlotte Foust [<A
href="mailto:cfoust@infostatsystems.com">mailto:cfoust@infostatsystems.com</A>]</FONT>
<BR><FONT size=2>Sent: Wednesday, July 23, 2003 12:36 PM</FONT> <BR><FONT
size=2>To: Access Developers discussion and problem solving</FONT> <BR><FONT
size=2>Subject: RE: [AccessD] Broken References in Runtime AXP</FONT> </P><BR>
<P><FONT size=2>Nope, sorry, but that didn't work for me in Access 2002. I
found that a</FONT> <BR><FONT size=2>long time ago, but it did not result in
either a fixed reference or a</FONT> <BR><FONT size=2>compiled application,
although the reference "thought" it was fixed. I</FONT> <BR><FONT
size=2>had to work my way through to something that would work reliably
and</FONT> <BR><FONT size=2>permanently when a customer opened the application
using a runtime</FONT> <BR><FONT size=2>installation. </FONT></P>
<P><FONT size=2>Charlotte Foust</FONT> </P>
<P><FONT size=2>-----Original Message-----</FONT> <BR><FONT size=2>From: Marcus,
Scott (GEAE, Contractor) [<A
href="mailto:scott.marcus@ae.ge.com">mailto:scott.marcus@ae.ge.com</A>]
</FONT><BR><FONT size=2>Sent: Wednesday, July 23, 2003 9:00 AM</FONT> <BR><FONT
size=2>To: 'Access Developers discussion and problem solving'</FONT> <BR><FONT
size=2>Subject: RE: [AccessD] Broken References in Runtime AXP</FONT> </P><BR>
<P><FONT size=2>Charlotte,</FONT> </P>
<P><FONT size=2>I know that I'm jumping in the middle here but...</FONT> </P>
<P><FONT size=2>Your solution is in the Microsoft knowledge base. The article is
194374.</FONT> <BR><FONT size=2>I have used this method for years. It works very
well</FONT> </P>
<P><FONT size=2>Here is a link to the article:</FONT> <BR><FONT size=2><A
href="http://support.microsoft.com/default.aspx?scid=kb;en-us;194374"
target=_blank>http://support.microsoft.com/default.aspx?scid=kb;en-us;194374</A></FONT>
</P>
<P><FONT size=2>Scott</FONT> </P>
<P><FONT size=2>-----Original Message-----</FONT> <BR><FONT size=2>From:
Charlotte Foust [<A
href="mailto:cfoust@infostatsystems.com">mailto:cfoust@infostatsystems.com</A>]</FONT>
<BR><FONT size=2>Sent: Wednesday, July 23, 2003 12:01 PM</FONT> <BR><FONT
size=2>To: Access Developers discussion and problem solving</FONT> <BR><FONT
size=2>Subject: RE: [AccessD] Broken References in Runtime AXP</FONT> </P><BR>
<P><FONT size=2>OK, here's the situation as it stands. Using a query, as
Gustav</FONT> <BR><FONT size=2>suggested, seems to give me an accurate way to
test for a broken</FONT> <BR><FONT size=2>reference. I call that test from
my FixReference routine and if it's</FONT> <BR><FONT size=2>true, I repair the
library reference by removing it add adding it back.</FONT> <BR><FONT
size=2>RefLibPaths gives me the correct path for adding it back, so that
part</FONT> <BR><FONT size=2>is easy. This works in runtime or full
installation and only performs</FONT> <BR><FONT size=2>the fix if the reference
is actually broken. </FONT></P>
<P><FONT size=2>The compile issue is a bit trickier and I found a kludge, but
I'm open</FONT> <BR><FONT size=2>to suggestions if anyone has them. The
undocumented SysCmd(504, 16483)</FONT> <BR><FONT size=2>doesn't error but it
doesn't seem to compile either. I ran into a post</FONT> <BR><FONT
size=2>on the net that suggested it might not work with modules open
(didn't</FONT> <BR><FONT size=2>say how you ran code otherwise, but I assume the
reference was to the 97</FONT> <BR><FONT size=2>VBE) so I started thinking
"macro". If found that if I modify my</FONT> <BR><FONT size=2>autoexec
macro, it will run the compile for me. So an autoexec that</FONT>
<BR><FONT size=2>looks like this compiles the app after fixing the
reference:</FONT> </P>
<P><FONT size=2>Condition
Action
Command</FONT> <BR><FONT
size=2>IIf(FixReference()=True,True,False)</FONT> <BR><FONT
size=2>...
RunCommand</FONT> <BR><FONT
size=2>CompileAndSaveAllModules</FONT>
<BR>
<FONT size=2>OpenForm</FONT>
<BR><FONT size=2>frmSplash</FONT> </P>
<P><FONT size=2>Charlotte Foust</FONT> <BR> </P></BODY></HTML>