Bde Error 12550
Contents |
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 bde error 12550 $31 6 version 3.51 we get something like Invalid configuration parameter: Alias: database_alias
Bde Fehler 12550
BDE Error 12550 [0x31][0x6] I've searched the list archives and realize that some people have occasionally invalid configuration parameter alias bde come across this problem but haven't found a solution or an indication of what the problem is ... Borland,s web site says of BDE Error 12550 bde error 13059 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". Has anyone run into this before ? _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com --------------------------------------------------------------------- Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail
View All Answers My Questions Articles Tutorial Tips, Tricks & Techniques News Database Support Community Forums Search Recent DiscussionsResourcesQuality PortalEvents CalendarEmbarcadero on YouTube Job BoardRegistered User DownloadsTrial Downloads Books Login Register HomeArticlesTips, Tricks & TechniquesDATABDE 12550 Invalid configuration parameter error BDE 12550 Invalid configuration parameter error Written by Embarcadero USA. Posted in DATA Question and Answer Database FAQ: FAQ4559B - BDE 12550 Invalid configuration parameter http://lists.mysql.com/mysql/99333 error Category: BDE Platform: All-32Bit Product: All-CBuilder, BC++5.x, C++Builder1.0, C++Builder3.x, C++Builder4.x, Delphi2.x, Delphi3.x, Delphi4.x, VdBase7.x, Question: What might be causing the error BDE 12550 Invalid configuration parameter? Answer: 12550 Invalid configuration parameter. One possible cause for the error: ODBC ALIASES. When creating and/or using a BDE alias that is using an http://community.embarcadero.com/article/technical-articles/146-data/11990-bde-12550-invalid-configuration-parameter-error 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". 7/13/99 10:10:56 AM Article originally contributed by Bill Curtis Tags: Delphi C++Builder Database < Prev Next > Tweet About Embarcadero USA Gold User, Rank: 4, Points: 574 Add as friend View Profile More from this Author Share It Latest News InterBase and Windows 10 Anniversary Update Windows 10 Anniversary Update and RAD Studio Cool App Winner: EarMaster for iPad Product Roadmap August 2016 Product Roadmap Update Article Tags Delphi C++Builder Platforms JBuilder Tools InterBase Programming Linux FireMonkey Database Components Win32 HTML5 Builder Pr
this morning, everything was working fine. Now http://lists.mysql.org/mysql/99010 when I attempt to connect to the database I am getting an error: "Invalid configuration paramater" with a BDE error code of 12550. The only thing I have done was to install Install bde error Shield for Delphi 4 and run an installation setup so I could install my program on a user's machine (that's another horror story). I've tried uninstalling the database from the BDE administrator then uninstalling and reinstalling the DB2 client then bde error 12550 adding the database back into the BDE but to no avail. I am getting this error in the BDE as well as the application. Any help? Pam Other Threads 1. MySQL+MyODBC+BDE -> invalid configuration error (BDE Error 12550) 2. BDE Error Code 12550 3. BDE error $251E - An Error occurred while attempting to initialize the BDE 4. BDE Error $210D and BDE Error $2A04, dilemma !!! 5. BDE error Record/Key Deleted BDE-Error:8708 6. Error occured while trying to initialize BDE, Error in modifying BDE 7. Application without BDE, but still BDE error? 8. BDE Error $2104 calling BDE API 9. BDE Error - but not using BDE 10. BDE Error 210D when starting more than 2 BDE Apps
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