[AccessD] Broken References in Runtime AXP

Jim,
 
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.
 

Charles Wortz 
Software Development Division 
Texas Education Agency 
1701 N. Congress Ave 
Austin, TX 78701-1494 
512-463-9493 
CWortz at tea.state.tx.us 

-----Original Message-----
From: Hale, Jim [mailto:jim.hale at fleetpride.com] 
Sent: Wednesday 2003 Jul 23 14:09
To: 'Access Developers discussion and problem solving'
Subject: RE: [AccessD] Broken References in Runtime AXP



The final solution would make a great article (he suggested beggingly) 
Jim Hale 

-----Original Message----- 
From: Charlotte Foust [mailto:cfoust at infostatsystems.com] 
Sent: Wednesday, July 23, 2003 12:36 PM 
To: Access Developers discussion and problem solving 
Subject: RE: [AccessD] Broken References in Runtime AXP 


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 


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://databaseadvisors.com/pipermail/accessd/attachments/20030723/63b680e6/attachment-0001.html>