Bde Error 12550 Oracle
Hi, > -----Original Message----- > From: Guido Sohne [mailto:caught_one@stripped] > Sent: Friday, February 08, 2002 6:54 AM > To: mysql@stripped > Subject: MyODBC BDE invalid configuration error (BDE Error 12550) > > > We're running a MySQL 3.23.47 server on Windows 98, and when trying to > connect to BDE version 3.0 (bundled with Borland C++ Builder 1) using > MyODBC version 3.51 we get something like > > > Invalid configuration parameter: > Alias: database_alias > > BDE Error 12550 [0x31][0x6] > > > I've searched the list archives and realize that some people have > occasionally come across this problem but haven't found a solution or an > indication of what the problem is ... Is it possible for you to trace MS ODBC DM calls and send that log ? That enables the clear picture of what is happening. I tried to download the eval copy of Borland C++ Builder to give a try, but it is ~140 MB, so waiting for your log. If it doesn't help, then I will go ahead and give a try by downloading. > > Borland,s web site says of BDE Error 12550 > > > 12550 Invalid configuration parameter. > > One possible cause for the error: > ODBC ALIASES. > When creating and/or using a BDE alias that is using > an ODBC DSN make sure that the ALIAS parameter "ODBC DSN" is > set to the DSN that you wish to use and that has been created > using ODBC Manager. Available ODBC DSN's can be chosen from > the parameter's drop-down edit using the BDE Administrator. > > Another possible cause: > Using ISAPI app and ODBC against NT web server. > ODBC DSN on NT machine should be set to "system" > instead of "user". Did you tried with the 'system dsn' or 'file dsn' ? And whats the outcome ? For more information on different types of DSNs, refer to http://www.mysql.com/products/myodbc/faq.html#DSN_Types Regards, Venu -- For technical support contracts, go to https://order.mysql.com __ ___ ___ ____ __ / |/ /_ __/ __/ __ \/ / Mr. Venu Professional InstallShield Professional Version 6.x installshield.is6.objects URGENT! - BDE Error 12550 If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. Results 1 to 1 of 1 Thread: URGENT! - BDE Error 12550 Thread Tools Show Printable Version Subscribe to this Thread… Display Linear Mode Switch to Hybrid Mode Switch to Threaded Mode 04-05-2000,12:00 AM #1 NewsArchive View Profile View Forum Posts Uber User (1000+ Posts) http://lists.mysql.com/mysql/99420 Join Date Oct 2001 Posts 44,727 URGENT! - BDE Error 12550 InstallShield Professional 6.1 BDE 5.1 ODBC 3.51 NT 4.0 (SP6) ----------------------------------------------------- I'm installing a DSN through the BDE Object. When using the BDE Object to install a DSN on a target machine, it states, upon completion of BDE Object wizard, that you need to also install the ODBC Object, so I've included both in my setup. I've noticed in BCB4's https://community.flexerasoftware.com/showthread.php?66559-URGENT!-BDE-Error-12550 SQL Explorer, that my datasource is there, but after logging into it, it "pops" an error window. If I right click on my DSN name(in SQL Explorer) and selected Delete from the pop up menu, it goes away. Exiting from SQL Explorer and restarting it, shows my DSN is still connected and then, and only then, I can log into it with no errors. The error I'm seeing is: BDE Error: 12550 [$31] [$6] Invalid configuration parameter. I'm wondering if the two objects (BDE and ODBC) are both trying to set the DSN and therefore, that's why I can delete it but it still be there.... Also, with the BDE and ODBC Objects that I need for my installation, when the files are being copied, there is a LONG delay when copying the file IDAPI32.OLD (this file is not mentioned in the "Files Installed by this object" section of the InstallShield Object for BDE 5.1 text. I feel this IDAPI32.OLD file has incorrect information and is the cause my connection problems. Any ideas???? -- Trudy Reiser trudyw@leapfrog-smart.com Leapfrog Smart Products, Inc. Building Smart Solutions for a Dynamic World Quick Navigation installshield.is6.objects Top Site Areas Settings Private Messages Subscriptions Who's Online Search Forums Forums Home Forums Products AdminStudio AdminStudio Compatibility Sol from GoogleSign inHidden fieldsSearch for groups or messages Paradox Databases, Windows 7 Windows 7 can be very restrictive towards applications written for the previous versions of Windows. This is the case with the Borland Database Engine (BDE), which is not capable of running in Windows7 unless two settings have been changed: A permission for the BDE must be given in the windows registry database. A BDE attribute named "Net Dir" must be configured to an arbitrary folder other than the root drive (C:). This configuration is done in the "BDE Administrator" program that's installed with the BDEInfoSetup utility. 1. First, configure the permission for the BDE in the registry… Make sure you are logged into your Windows7 machine with an administrator account. Then follow these directions: Go to Start | Run… Type regedit… Open the HKEY_LOCAL_MACHINE branch. Open the SOFTWARE branch. Right-Click on the entry labeled "Borland". In the menu that shows select Permissions. The following dialog will appear: Click "Users". Under "Permissions for Users ", select "Allow" for Full Control. Then click OK. Click OK to exit the Registry Key Permissions dialog box. Exit the Registry Editor window 2. Next the Borland Database Engine must be configured… The Borland Database Engine makes use of a special file called "Pdoxusrs.net" (the purpose of which is beyond the scope of this document). The default setting for the placement of this file is in the root of drive C, which will fail under Windows Windows7, as this operating system does not permit new files to be created here. However, it is permitted to designate any subfolder for the "Pdoxusrs.net" file to be placed. The name of this new folder is of minor importance and could be named anything you like. For example, here we will choose "BDEShare". (The name doesn't matter. It just needs to be any folder other than the root drive.) So let's stick with this example. Create a subfolder off the root drive C and name it "BDEShare". So the file path for this new subfolder will be "C:BDEShare". Remember this string value because you will need to enter it below. Now the BDE must be configured to use the new folder. This is done in the Windows control panel, where you will find an applet named "BDE administrator". Note that you will only see this afte