URGENT!!!! Need some help with PROGRESS error!!!

Sorry for the alert post, but I have been working at this for 2 days now and I am SOOOOOOOOO close to tossing our database server out of the window.

I got the Merant 3.6 drivers configured. I can use an ADO string from a VB6 environment to return LIVE, REAL-TIME DATA!!!! GREAT NEWS!!!!! However......

If I use the SAME connection string in an ASP application, I receive the following error:

Microsoft OLE DB Provider for ODBC Drivers (0x80004005)
[MERANT][ODBC PROGRESS driver]Optional feature not implemented.

The only thing I found on this forum that sounded similar can be found on this thread:


If anyone can offer help, it would be GREATLY appreciated. This has been completely frustrating and I am VERY, VERY close to a solution, it is the last piece of the puzzle that is killing me.

Thanks a million in advance.
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

jrb1senior developerCommented:
OK, some environment variables must be set on the server:

DLC=<path to dlc>
IDLC=<path to dlc>
PROMSGS=<path to dlc>\promsgs
IPROMSGS=<path to dlc>\promsgs
PROOIBRK=<path to dlc>\bin\oibrkr32.exe
PROOIDRV=<path to dlc>\bin\oidrvr32.exe

These have to be set up as SYSTEM variables.

If that doesn't help, the problem may be with your ODBC settings.  Is your OIBroker on the same machine as the DB?


Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
iptraderAuthor Commented:
Thanks for your input.  I added the last 2 environment variables, as I already had the others.  The page loads now, no more error!  However, the SQL string returns NOTHING.  Any pointers?


jrb1senior developerCommented:
Haven't seen that before...can you post a code snippet?
iptraderAuthor Commented:
Happy to.  Here is the code I am using for the sample page (just to make a damn connection and return data in a control object :) )


Option Explicit
Dim RS
Dim sSelect

<link href="stylesampledb.css" rel="stylesheet" type="text/css">
<title>Sample Database Connection Application</title>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">

 <!--#include file="CommonAspScripts/dbconnection.asp"-->
  <!--#include file="Include/header.asp"-->

  <table border="0" align="center" cellpadding="0" cellspacing="0" id="table">
      <td> <select name="cbShipCode">
                        sSelect = "select ship-code from shipcode"
                        Set RS = Server.CreateObject("ADODB.RecordSet")
                        On Error Resume Next
                        RS.Open sSelect,AdoConnection,adOpenForwardOnly,adLockReadOnly      
                        If Err.number<>0 then
                              Response.Redirect "CommonAspScripts/ErrorPage.asp?Errnum="& err.number &"&ErrDesc=" & Err.Description
                        End If
                        Do while Not RS.EOF
                              Response.Write "<Option>" & RS("cbShipCode") & "</option>"

<!--#include file="Include/footer.asp"-->


Here is the code for the dbconnection.asp include file:


<!--#include file="adovbs.inc"-->
Dim AdoConnection
If Not IsObject(AdoConnection) then
      Set AdoConnection = Server.CreateObject("ADODB.Connection")
      On Error Resume Next
      AdoConnection.Open "Provider=MSDASQL.1;Persist Security Info=false;Data Source=SL402;Initial Catalog=ac"
      If Err.number<>0 then
            Response.Redirect "CommonAspScripts/ErrorPage.asp?Errnum="& err.number &"ErrDesc=" & Err.Description
      End if
End If


If I use the same EXACT code against a SQL Server 2000 database, with a different ADO connection string it works JUST FINE.  Whatever this is, it is WEIRD.


iptraderAuthor Commented:
Syntax error.  Never mind.  Your first piece of advice worked and now I am returning records like it's going out of style ;)


It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.