Error Message

M

Mike

After installing the BTR2 patch, everything worked great until I ran a
program called ACS (Automated Church Software) that I use to track
contributions for the church. I received this error message "Exception
EDBEnginError in module ASPE.exe at 00209406. Operation not applicable". I
figured there was a conflict between the two although they weren't running a
the same time. so I removed Office and ACS worked. I reinstalled Office
without BTR2 patch and ACS worked when I Installed the Patch ACS stopped
working. I use Office to put together all my reports for the church, Office
XP works fine. Does any of the office programs use the Borland Database
Engine? I think something was changed in that.
Thanks
Mike
 
B

Bob Buckland ?:-\)

Hi Mike,

There was a 'branding' change in B2TR that affects apps that use the Borland Database Engine (BDE) that MS is currently reviewing.
The error message you posted is a variant of others reported, but not an exact match.

There are a couple of workarounds you can try, that others have reported helped via editing registry entries, but be cautious on
later using either Office 2007 repair or Office 2007 diagnostics as those features can 'repair' things back to the defaults.

Please post back on the result of trying these changes to let us know if things are again functioning for you with Office2007 Beta 2
with the Beta 2 Technical Refresh Patch update(B2TR) and your Borland Data Engine (BDE) based product, and any side effects you may
note.

Before modifying the registy backup the HKEY_LOCAL_MACHINE (HKLM)
branch at
HKEY_LOCAL_MACHINE\Software\ODBC

Note: HKEY_LOCAL_MACHINE is shown as HKLM below for space:

A. HKLM\Software\ODBC\ODBCINST.INI\Paradox
Replace 'Paradox' with 'Microsoft Paradox'

B. HKLM\Software\ODBC\ODBCINST.INI\ODBC Drivers\Paradox
Replace 'Paradox' with 'Microsoft Paradox'

C. HKLM\Software\ODBC\ODBCINST.INI\dBase
Replace 'dBase' with 'Microsoft dBase'

D. HKLM\Software\ODBC\ODBCINST.INI\ODBC Drivers\dBase
Replace 'dBase' with 'Microsoft dBase'

One customer has reported that the following change may help the changes from being undone by MS Office 2007 Diagnostics (lines may
wrap around)

E. HKLM\Software\Borland\Database Engine\Settings\Drivers\ParadoxUnit
Add: new String value 'DLL'
Add: new String value 'DLL32'
leave the 'value' settings for those strings blank.

======================
After installing the BTR2 patch, everything worked great until I ran a program called ACS (Automated Church Software) that I use to
track
contributions for the church. I received this error message

"Exception EDBEnginError in module ASPE.exe at 00209406. Operation not applicable". I figured there was a conflict between the two
although they weren't running a the same time. so I removed Office and ACS worked. I reinstalled Office without BTR2 patch and ACS
worked when I Installed the Patch ACS stopped working. I use Office to put together all my reports for the church, Office XP works
fine. Does any of the office programs use the Borland Database
Engine? I think something was changed in that.

Thanks
Mike>>
--
I hope this helped you,

Bob Buckland ?:)
MS Office system products MVP

LINKS to the 2007 Office System

1. Free MS Office 2007 book from MS Press, 213 pages:
http://microsoft.com/learning/office2007/default.mspx#booksfrommspress

2.. Office 2007 Beta 2 Online Test Drive, Downloadable beta,
e-learning courses, doucmentation and movies:
http://microsoft.com/office/preview

3. Send 2007 Office System Beta 2 feedback directly to the MS Office 2007 product team with this feedback tool:
http://sas.office.microsoft.com/

4. Try the 2007 OfficeOnline preview website , without Office2007

a. Install the ActiveX access control
http://office.microsoft.com/search/redir.aspx?AssetID=XT101650581033

b. then visit
http://officebeta.iponet.net
 
M

Mike

Bob,
You people are great!! The fix worked. I have a question about the E. part
of the fix. My registry doesn't show
"HKLM\Software\Borland\Database Engine\Settings\Drivers\ParadoxUnit" mine
only has the following folders
1. HKLM\Software\Borland\Database Engine\Settings\Drivers\INIT
2. HKLM\Software\Borland\Database Engine\Settings\Drivers\Table Create
do I need to add the missing HKLM\Software\Borland\Database
Engine\Settings\Drivers\ParadoxUnit
Thanks again for your help.
Mike
 
B

Bob Buckland ?:-\)

Hi Mike,

Thank you for the followup and glad to hear that the first part seems to be working.

Sorry, a significant typo on my part in "E."
\ParadoxUnit should have been
\Paradox\Init and I left out a tier :(

Please keep in mind that these are user workarounds, and MS is still testing <g> :( It's not clear if this will affect any of the
MS app functionality.

This should be more helpful for 'E.'

E. For each of the following add 2 new string values

HKLM\Software\Borland\Database Engine\Settings\Drivers\Paradox\Init
Add: new String value 'DLL'
Add: new String value 'DLL32'
leave the 'value' settings for those strings blank.

HKLM\Software\Borland\Database Engine\Settings\Drviers\DBASE\Init
Add: new String value 'DLL'
Add: new String value 'DLL32'
leave the 'value' settings for those strings blank.

If those added entries already exist then it may be helpful to
change

HKLM\Software\Borland\Database Engine\Settings\DBASE
to
HKLM\Software\Borland\Database Engine\Settings\Microsoft DBASE

Please post back with your results. As I'm hoping you're running the Beta on a 'test machine' it may be helpful to test the
resiliency of these entries if after making the changes you

(1) Export from RegEdit the keys you changed. (probably a good
thing to have anyway at this point <g>)

(2) Set a restore point, then run Office Diagnostics from
Start=>Programs=>Microsoft Office=>Microsoft Office Tools
to see if it does again break the entries.
If it does, you'd need to manually make the entries again
or reimport the keys you saved in step 1.

Please use Start=>Search to locate the Offdiagreport.cab file that Office diagnostics creates and email it to me.

=================
Bob,
You people are great!! The fix worked. I have a question about the E. part
of the fix. My registry doesn't show
"HKLM\Software\Borland\Database Engine\Settings\Drivers\ParadoxUnit" mine
only has the following folders
1. HKLM\Software\Borland\Database Engine\Settings\Drivers\INIT
2. HKLM\Software\Borland\Database Engine\Settings\Drivers\Table Create
do I need to add the missing HKLM\Software\Borland\Database
Engine\Settings\Drivers\ParadoxUnit
Thanks again for your help.
Mike>>
 
M

Mike

Hello Bob,
I'm running four computers. I'm running the Office beta on two test
computers. The two test computers are mirrors of two other computers as far
as programs and files. I sent the file you requested to the email address in
your profile, I hope that is the place you wanted me to send it. The new
location "HKLM\Software\Borland\Database
Engine\Settings\Drivers\Paradox\Init" doesn't exist on the computer I'm
currently using. After I made the changes in the first part the ACS program
worked fine. I didn't notice any changes in any of the Office programs I
regularly use. So I ran the Office Diagnostics and the ACS program would not
start, same error message as before. So I ran regedit and noticed that all of
the changes I had made, had been saved and the original entries had been
rewritten. The dbase that I had changed to Microsoft dbase was there as was
the new dbase.
So I simply deleted the entries added by Office Diagnostics and the ACS
program started and appeared to work as advertised.
I hope I didn't confuse you with this convoluted explanation. If you would
like to try something else just let me know.
Thanks
Mike
 
M

Mike

Bob,
On test computer #2 the entries for E. in the regestry were there, I changed
them as instructed, ran the Office Diagnostics and the ACS program worked
fine after. I didn't need to edit the regestry as I did on computer #1. Why
would computer #1 not have the regestry keys like computer #2? The Computers
are the same as far as software and files. I emailed the .cab file from
computer # 2 to you a few minutes ago.
Mike
 
B

Bob Buckland ?:-\)

Hi Mike,

Interesting. Thank you for sending the files and for the followup . I'll take a look through them shortly to see if what I can
spot as far as differences.

Do you have MS Access 2007 on both of these computers?
Do you have any pre-2007 MS Office software on the computers?
Was MS Works on either computer at some point?
Was Act! on either computer at some point?

Are there any other programs/utilities that you're aware of on these computers that use ODBC files (Paradox, dBase, etc)?

============

==========
<<Bob,
On test computer #2 the entries for E. in the regestry were there, I changed
them as instructed, ran the Office Diagnostics and the ACS program worked
fine after. I didn't need to edit the regestry as I did on computer #1. Why
would computer #1 not have the regestry keys like computer #2? The Computers
are the same as far as software and files. I emailed the .cab file from
computer # 2 to you a few minutes ago.
Mike >>
 
M

Mike

Good morning,
Access 2007 are on both computers (never used). No Works or Act on either
computer. Both computers had Office XP before the Beta was installed. As far
as other programs, Adobe Suite CR1, Coreldraw 12 and Quickbooks Pro. If you
need any other info please let me know.
Mike
 
P

plonge49

Hello
i have a similary problem with BDE and Interbase Driver
Since i installed the B2TR release of office 2007, i have the message
'operation non applicable' (in french version)
What can i modify to resolve this problem

Thanks
 
B

Bob Buckland ?:-\)

Hi Plonge,

There was a 'branding' change in B2TR registry entries that affects apps that use the Borland Database Engine (BDE) that MS is
currently reviewing for changes to make to the Office 2007 release product. I'm sorry that I don't have French language registry
equivalents of the items below.

There are a couple of workarounds you can try, that others have reported helped via editing registry entries, but be cautious on
later using either Office 2007 repair or Office 2007 diagnostics as those features can 'repair' things back to the defaults.

Please post back on the result of trying these changes to let us know if things are again functioning for you with Office2007 Beta 2
with the Beta 2 Technical Refresh Patch update(B2TR) and your Borland Data Engine (BDE) based product, and any side effects you may
note.

Before modifying the registy backup the HKEY_LOCAL_MACHINE (HKLM)
branch at
HKEY_LOCAL_MACHINE\Software\ODBC

Note: HKEY_LOCAL_MACHINE is shown as HKLM below for space:

A. HKLM\Software\ODBC\ODBCINST.INI\Paradox
Replace 'Paradox' with 'Microsoft Paradox'

B. HKLM\Software\ODBC\ODBCINST.INI\ODBC Drivers\Paradox
Replace 'Paradox' with 'Microsoft Paradox'

C. HKLM\Software\ODBC\ODBCINST.INI\dBase
Replace 'dBase' with 'Microsoft dBase'

D. HKLM\Software\ODBC\ODBCINST.INI\ODBC Drivers\dBase
Replace 'dBase' with 'Microsoft dBase'

Two customers have reported that the following change may help the changes from being undone by MS Office 2007 Diagnostics (lines
may
wrap around)

E. For each of the following add 2 new string values

HKLM\Software\Borland\Database Engine\Settings\Drivers\Paradox\Init
Add: new String value 'DLL'
Add: new String value 'DLL32'
leave the 'value' settings for those strings blank.

HKLM\Software\Borland\Database Engine\Settings\Drviers\DBASE\Init
Add: new String value 'DLL'
Add: new String value 'DLL32'
leave the 'value' settings for those strings blank.

If those added entries already exist then it may be helpful to
change

HKLM\Software\Borland\Database Engine\Settings\DBASE
to
HKLM\Software\Borland\Database Engine\Settings\Microsoft DBASE

Please post back with your results, also the exact error message and the version of the Borland Data Engine (BDE) you are using. As
I'm hoping you're running the Beta on a 'test machine' it may be helpful to test the resiliency of these entries if after making the
changes you

(1) Export from RegEdit the keys you changed. (probably a good
thing to have anyway at this point <g>)

(2) Set a restore point, then run Office Diagnostics from
Start=>Programs=>Microsoft Office=>Microsoft Office Tools
to see if it does again break the entries.
If it does, you'd need to manually make the entries again
or reimport the keys you saved in step 1.

Please use Start=>Search to locate the Offdiagreport.cab file that Office diagnostics creates and email it to me.

============
Hello
i have a similary problem with BDE and Interbase Driver
Since i installed the B2TR release of office 2007, i have the message
'operation non applicable' (in french version)
What can i modify to resolve this problem

Thanks >>
 
P

plonge49

Hello Bob
I don't use ODBC neither DBASE, PARADOX, ..

I use natif Interbase (with Delphi ) and i don't think the change you
tell to me are for this case.
This error is only when in a Query i use the propertie
'cacheupdates=true'
Except this case, access to database are OK

I use BDE 5.2


My problem is not isolated, i saw exactly the same problem on others
forum without any solution

Thanks for your help
 
P

plonge49

I solved my problem
I have deleted HKLM\software\odbc\odbcinst.ini\odbc drivers\Parado
 
Top