Hi Cedric,
There was a 'branding' change in B2TR registry entries that affects apps that use the Borland Database Engine (BDE) that MS is
currently reviewing. You didn't post the error message you posted, and the following are 'test' case workarounds that may not apply
if your error message isn't one that has been mentioned before.
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,
After updating my office 2007 install with the TR, an other applications
written in Delphi and using Borland database raised an error at start.
Everything was working properly before the TR update. Does my problem come
from my delphi program (I don't think so, 'cause it was working with Office
2007 Beta 2) or from the TR update ? >>
--
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