Re: old school com on Win2k3 Adv Server?
From: jajaj (jaja_at_joespam.com)
Date: 04/22/04
- Next message: Kolmyk AE: "ATL: Automation vs. TLB usage"
- Previous message: Kim Gräsman: "Re: problem assigning double as defaultvalue"
- In reply to: Brian Muth: "Re: old school com on Win2k3 Adv Server?"
- Next in thread: Brian Muth: "Re: old school com on Win2k3 Adv Server?"
- Reply: Brian Muth: "Re: old school com on Win2k3 Adv Server?"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 22 Apr 2004 06:31:34 -0500
this sounds really weird, but unless i install it as a COM+ application,
it doesn't seem to have access to the environment (like the PATH) can't
read it's .ini file (it's an older API i'm working with) from the
system32 directory and such.
As written the COM object works fine on all boxes i've tested except
this one. On this particular box the underlying API fails after being
called a set number of times (a bit less than 4000) sounds like i'm
blowing a buffer, I know, but the API in question has been use in a
variety of environments for many years without seeing this behavior
Brian Muth wrote:
> COM objects work just fine on Win2003.
>
> What exactly is the problem you are encountering? Just saying it "doesn't
> work well" isn't very helpful.
>
> Brian.
>
- Next message: Kolmyk AE: "ATL: Automation vs. TLB usage"
- Previous message: Kim Gräsman: "Re: problem assigning double as defaultvalue"
- In reply to: Brian Muth: "Re: old school com on Win2k3 Adv Server?"
- Next in thread: Brian Muth: "Re: old school com on Win2k3 Adv Server?"
- Reply: Brian Muth: "Re: old school com on Win2k3 Adv Server?"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|