[AccessD] Broken References in Runtime AXP

Hi Scott

Well, you must be lucky, that's all I can say.
You are right about the SysCmd call, it is not a bug. The bug I'm
referring to (mentioned before in this thread) is the IsBroken
property which doesn't work reliably.

/gustav


> Fixing the Ref's has always worked for me in Access97. AccessXP may be a
> different beast all together. That's why I mentioned that I may be out of
> line by jumping in the middle of the conversation. The Knowledgebase article
> says that it is for Access97.

> Are you saying that the SysCmd() is flaky in Access97? As I said before, it
> has always worked for me no matter where I call it from (code, macro, or
> debug window).

> I wouldn't call this a bug. It's undocumented and therefore not supported.
> How can something not supported and undocumented, being broken, be a bug?

> Scott

> -----Original Message-----
> From: Gustav Brock [mailto:gustav at cactus.dk]
> Sent: Wednesday, July 23, 2003 1:40 PM
> To: Access Developers discussion and problem solving
> Subject: Re: [AccessD] Broken References in Runtime AXP


> Hi Scott

> Charlotte can speak for herself, I know, but this article doesn't
> mention Access XP (two version after A97) where you could have
> expected this bug to have been corrected fully.

> Further, both Charlotte and I have found that this SysCmd() thing
> doesn't work when called from code. The only way I've seen it work is
> when called manually from the debug window.

> This is easy to confirm because the compile icon in the commandbar is
> greyed out when the app is compiled.

> /gustav


>> 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