Icon View Thread

The following is the text of the current message along with any replies.
Messages 1 to 4 of 4 total
Thread Crazy Situation Error $2108
Tue, Aug 21 2007 5:30 PMPermanent Link

"Huhtaman"
Hello All:

   All my applications are DBISAM only (Version 1 - an antique) - no BDE -
ever. I just changed 1 line of code in a critical utility - and now - it
wont run.

  When the app is run it gets a $2108 error initializing the BDE. This
error usually is associated with an improper BDE installation.

  But - I never used the BDE - ever - my one new line of code is to add a
password to the current session so the user is not propmted for passwords.

  I added  Session.AddPassword('ATHUH'); in each of the 6 procedures - and
now - kaboom.

   I rolled back the utility - and the prior version works great.

There are no references I can find in my code to the BDE.

Can anybody give me a hint as to how I can find out what has caused this to
occur ???


Thank you

Neil Huhta

Tue, Aug 21 2007 8:37 PMPermanent Link

Sean McCall
You can remove the BDE dependant .DCUs from your machine or move them
out of the search path and if there is a reference to the BDE it will
generate a compilation error. Be sure to scan the drive for the DCUs so
you don't miss any. There must be a link somewhere to be getting a BDE
error.

Sean

Huhtaman wrote:
> Hello All:
>
>     All my applications are DBISAM only (Version 1 - an antique) - no BDE -
> ever. I just changed 1 line of code in a critical utility - and now - it
> wont run.
>
>    When the app is run it gets a $2108 error initializing the BDE. This
> error usually is associated with an improper BDE installation.
>
>    But - I never used the BDE - ever - my one new line of code is to add a
> password to the current session so the user is not propmted for passwords.
>
>    I added  Session.AddPassword('ATHUH'); in each of the 6 procedures - and
> now - kaboom.
>
>     I rolled back the utility - and the prior version works great.
>
> There are no references I can find in my code to the BDE.
>
> Can anybody give me a hint as to how I can find out what has caused this to
> occur ???
>
>
> Thank you
>
> Neil Huhta
>
>
Wed, Aug 22 2007 10:04 AMPermanent Link

Mauricio Campana Nonino
Neil Huhta

Sean is correct. A workaround is to explicit you want Session from dbisam instead bde

DBISAMTb.Session.AddPassword

Mauricio Campana Nonino
Nonino Software
Wed, Aug 22 2007 6:37 PMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Neil,

<< I added  Session.AddPassword('ATHUH'); in each of the 6 procedures - and
now - kaboom. >>

That line, by itself, won't cause the BDE to be loaded.  You must have the
dbtables unit referenced somewhere in your code.

--
Tim Young
Elevate Software
www.elevatesoft.com

Image