FAQ: DRS 2006 - Database related Problems 
FAQ 1: Audio Directories
I have problems inserting my mp3 files to the DRS 2006 database. After I have inserted a new file it won't play. Also the filename looks a little strange. It seems to be cut off. Where is the problem?
This is also a question we get quite often. You have to set 3 audio directories in the DRS 2006 Database Connector. These directories have to be real directories and not just the drive itself. So you have to use E:\MP3Data instead of just E:\. Underneath these main directories you can use as many subdirectories as you want. We have made this rather complicated way to locate your files because of the full networking features of DRS 2006. You can repair your database by deleting the corrupt files in the Database Connector ("Check Audio Integrity") or in the Audio Manager. Then you copy your mp3 files to one of the 3 directories and insert them again with the Audio Manager.
FAQ 2: Disappearing Audio or Titles Don't show
After inserting audio my titles don't appear, it's as if they just disappear.
Your first port of call should always be the Database Utility. From here you should choose HRDat.dbf, and then go to Tools > Reindex.
For version 3.0/Enterprise choose to reindex DRSMain.dbf.
Afterwards, Check Database Integrity via the Database Connector (Audio Manger Utilities>Check Database Integrity in version 3.0/Enterprise).
FAQ 3: New Files Do Not Show Up In On Air Studios
After inserting audio my titles don't appear in the On Air Studios.
Open your DRS 2006 Search Engine or locate Reset & Refresh in the Studio. Click this button. Now your files will appear.
FAQ 4: Suddenly an error message "Operation not applicable" after installing Service Pack 2 or Office 2007

I suddenly get error messages when using DRS 2006. I only installed the Service Pack 2 and Office 2007 Beta
Office 2007 beta 2 causes damage to the Borland Database Engine(BDE). The BDE is used by all DRS 2006 Packages. Some installations of the Office 2007 beta 2 suite have made changes to the windows registry that prevents the BDE from accomplishing certain communication tasks. This will render the user unable to edit certain fields in DRS 2006 and will return an error with a message like 'Operation not applicable'. The following registry entries must be added on an effected DRS 2006 Workstation to restore proper operation:

HKEY_LOCAL_MACHINE\SOFTWARE\Borland\Database Engine\Settings\DRIVERS\PARADOX\INIT
add 2 new "String Values" elements:
name = "DLL32" , value = blank
name = "DLL" , value = blank

HKEY_LOCAL_MACHINE\SOFTWARE\Borland\Database Engine\Settings\DRIVERS\DBASE\INIT
add 2 new "String Values" elements:
name = "DLL32" , value = blank
name = "DLL" , value = blank

If those added entries already exist then it may be helpful to
change
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'


Copyright © 1999-2008 by