[AccessD] Broken References in Runtime AXP

Yes, but I've tracked down the problem ... Or at least one of them.  I
had taken it on faith that the BrokenReference method would actually
return a -1 when a reference to another database was missing and that
the IsBroken property of the reference object would return a -1 in that
case as well.  Apparently, even fully disambiguated, that isn't true.
Now I need to figure out how to NOT run it every time the application
starts!  I had to resort to writing directly to a text file to figure
out where it was going haywire. 

Charlotte Foust

-----Original Message-----
From: Jim Dettman [mailto:jimdettman at earthlink.net] 
Sent: Thursday, July 17, 2003 9:51 AM
To: Access Developers discussion and problem solving
Subject: RE: [AccessD] Broken References in Runtime AXP


Charlotte,

  This is with a MDB and not a MDE correct?

Jim Dettman
President,
Online Computer Services of WNY, Inc.
(315) 699-3443
jimdettman at earthlink.net 

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Charlotte
Foust
Sent: Wednesday, July 16, 2003 7:11 PM
To: AccessD at databaseadvisors.com
Subject: [AccessD] Broken References in Runtime AXP


Does anyone know if it is possible to repair a broken reference in 2002
under the runtime executable?   I have scoured the MSKB and the web and
can't find anything that says you can't ... Except that my experience in
trying it is that it simply doesn't happen, no matter how carefully I
disambiguate the code.  If anyone has ideas, I'm open to suggestion.

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