Very Computer

by **JCDNC** » Fri, 30 Jul 1999 04:00:00

We're using the 4.0 BDE with Paradox v8, Netware 4.1, Windows 95, 32 bit.
We're finding that the IDAPI.Cfg is getting modified - unknowingly - by users
with read/write rights to the location of the BDE. The modifiers have all been
network engineers with supervisory rights to just about anywhere. They do not
use BDEADMIN.Exe. We think it has something to do with a not so good Corel
integration of the BDE into their suite. What happens is that the LEADINGZEROD
and the FOURDIGITYEAR parameters are changed to FALSE - even if we have the
IDAPI.Cfg flagged RO. We ruled out GroupWise, HEAT, and now think it is
WordPerfect causing the problem (the last modifier was using WP only). It's
very difficult to replicate, as we haven't pinned down the exact software
scenario. It's always a few hours later when I find the IDAPI has changed. In
any event, our Paradox apps become non-Y2K whenever this occurs, as date calcs
are effected. The only fix so far is to change the rights in the BDE directory
to RO for the modifier, which is unacceptable. I've never heard of other
software modifying the BDE just to suit its needs. We consider this a very
serious Y2K bug. Perhaps the Inprise-only 5.0+ BDE will resolve the problem?
Any ideas as to how this can happen? Comments?

by **Kasey Chan** » Fri, 30 Jul 1999 04:00:00

Check CorelCentral... That thing uses BDE.

Quote:> We're using the 4.0 BDE with Paradox v8, Netware 4.1, Windows 95, 32
bit.
> We're finding that the IDAPI.Cfg is getting modified - unknowingly -
by users
> with read/write rights to the location of the BDE. The modifiers have
all been
> network engineers with supervisory rights to just about anywhere.
They do not
> use BDEADMIN.Exe. We think it has something to do with a not so good
Corel
> integration of the BDE into their suite. What happens is that the
LEADINGZEROD
> and the FOURDIGITYEAR parameters are changed to FALSE - even if we
have the
> IDAPI.Cfg flagged RO. We ruled out GroupWise, HEAT, and now think it
is
> WordPerfect causing the problem (the last modifier was using WP only).
It's
> very difficult to replicate, as we haven't pinned down the exact
software
> scenario. It's always a few hours later when I find the IDAPI has
changed. In
> any event, our Paradox apps become non-Y2K whenever this occurs, as
date calcs
> are effected. The only fix so far is to change the rights in the BDE
directory
> to RO for the modifier, which is unacceptable. I've never heard of
other
> software modifying the BDE just to suit its needs. We consider this a
very
> serious Y2K bug. Perhaps the Inprise-only 5.0+ BDE will resolve the
problem?
> Any ideas as to how this can happen? Comments?

--
Kuo-Sheng "Kasey" Chang / spam-hater /
Paradox guru / X-Com Guru / Sci-Fi Fan /
Treknologist / Military buff / a guy (yes, male!)

Sent via Deja.com http://www.deja.com/
Share what you know. Learn what you don't.

by **Mike Bes** » Sat, 31 Jul 1999 04:00:00

The parameters you mention are stored in the Windows Registry and can be
changed there without reference to the BDEADMIN.exe. Is there a scenario
where the Resistry is controlled by you system admin guys and is restored to
a previous or default state on startup to prevent users from changing things
which would affect the network?

Mike Best

Mike Best Programming
Brisbane
Australia

>We're using the 4.0 BDE with Paradox v8, Netware 4.1, Windows 95, 32 bit.
>We're finding that the IDAPI.Cfg is getting modified - unknowingly - by
users
>with read/write rights to the location of the BDE. The modifiers have all
been
>network engineers with supervisory rights to just about anywhere. They do
not
>use BDEADMIN.Exe. We think it has something to do with a not so good Corel
>integration of the BDE into their suite. What happens is that the
LEADINGZEROD
>and the FOURDIGITYEAR parameters are changed to FALSE - even if we have the
>IDAPI.Cfg flagged RO. We ruled out GroupWise, HEAT, and now think it is
>WordPerfect causing the problem (the last modifier was using WP only).
It's
>very difficult to replicate, as we haven't pinned down the exact software
>scenario. It's always a few hours later when I find the IDAPI has changed.
In
>any event, our Paradox apps become non-Y2K whenever this occurs, as date
calcs
>are effected. The only fix so far is to change the rights in the BDE
directory
>to RO for the modifier, which is unacceptable. I've never heard of other
>software modifying the BDE just to suit its needs. We consider this a very
>serious Y2K bug. Perhaps the Inprise-only 5.0+ BDE will resolve the
problem?
>Any ideas as to how this can happen? Comments?

by **JCDNC** » Sat, 31 Jul 1999 04:00:00

Thanks for your comments. I'm aware the registry can be changed, and the
scenario you're speaking of, but in this case the IDAPI.Cfg itself is being
changed - and it is not being done intentionally by those "system admin guys",
which I am not. I'm new with this newsGroup, but have programmed with dBase
and Paradox since 1981, and Delphi since 1995. No one knows the file is
getting changed until it is checked or until the Accounting Dept. tries to run
various Paradox reports with date calculations. So far, from the responses I'm
getting, it looks like the rogue software may be CorelCentral or the
WordPerfect Address book causing the problem. Upgrading to Corel version 9.0
may be the answer, but I'm sure you would appreciate it's not that easy to get
a state government to do that after convincing them they needed to upgrade from
7.0 to 8.0 so that GroupWise could be integrated properly for Y2K purposes. It
looks like Corel's attempt at BDE integration into their suite was more like
disintegration, and in my opinion they've totally lost sight of the big
picture: The Borland Database Engine. If you know of a patch please let me
know. Cheers, Mike.

by **Mike Irwin [CTech** » Sat, 31 Jul 1999 04:00:00

Already answered here

--
Mike Irwin It's not because things are hard that we
[Volunteer CTech Sysop, don't dare them; it's because we don't
not a Corel employee] dare them that they are hard - Seneca.

Very Computer

Y2K and Corel BDE Integration

Y2K and Corel BDE Integration

Y2K and Corel BDE Integration

Y2K and Corel BDE Integration

Y2K and Corel BDE Integration

Y2K and Corel BDE Integration