Search results for query: *

WOW! Great info DreXor! Do you know if the same applies, as it should, to InterDev 6.0? I use InterDev for all of my ASP development. Thanks again. I'll ask the Security Team for their help.

DreXor, How and where can I turn FP off? I'd like to explore this. Thanks.

bluecjh, I suggest you look at my thread titled "ASP Provider = Connection Error". Pyrohonnist offered a suggestion toward the bottom that worked. However, I've had to revisit this frequently and re-do it daily.

I'm quering an Oracle 8i table that contains manufacturer's part numbers in a catalog. Some of the name contain special characters (#,-, and /). Attempt to pass those values via ASP cause all kinds of problems. Does anyone have a work around? I've created functions in my ASP to do some...

Snowboardr, I want to try your code fix but don't quite understand what you're doing. Can you break it down for me... I'm a beginner. Thanks. Your code read: <% Dim Service_cd, desc1, desc2, desc3 '#put all data in a string... Service_cd = Server.URLencode(rst("Service_CD")) desc1 =...

You might want to try something like this: window.location.href = serverLocation + "user0=<UserName>&password0=<Password>&prompt0=" + reportgroup + "&prompt1=" + EntityList + "&prompt2=" + ShowDetail + "&prompt3=" + GroupOrder; OR window.location.href = serverLocation +...

You can't imaging my displeasure at arriving back at the same place. I do appreciate your help. If you recall the site offering information on this problem, let me know. YOu can email me direct at: JAntoine@bjc.org Thanks again.

Pyrrohonist, Althought your recommedations worked, I've had to monkey with the DSN and ASP code daily to make the connections work. Everyday, the old error pops up again. Now, I've removed and recreated the DSN and I'm still not able to get the page to display without errors. Any new ideas?

You should know that solution is really in 2 parts. First involves the steps you supplied. Next involves changing the text in my ASP code from: oConn.Open = "Provider=MSDAORA;Data Source=<Source>;User ID=<User>;password=<Password>;" To: With oConn .Provider="MSDAORA" .ConnectionString="Data...

Pyrrhonist, That worked!!!! I must have missed a step in an earlier attempt!!! THANKS!

Well I'm blue in the face with this. I've gone to Oracle and downloaded their lates drivers (9.2.0.6.0 that's suppose to be compatible with Windows 2003 server.) I've created new System DSN's and changed the connections string in my ASP code and still get the failures. There's a new failure...

Nada! I give up. I think I'm going to move back to Win2000 Pro and Oracle 8i client. I know that works. I sincerely appreciate your time and efforts to assist. Let me know if I may return the favor. You can reach me at: jantoine@bjc.org Jean

No, Pyrrhonist, that didn't do it. I also stopped and restarted the IIS server after making the change to my connection string. Thanks for the effort. Are you running 2000 or 2003 server; also, are you running Oracle? If so, what version of the Oracle client is installed on IIS?

Thanks Cassidy! It's worth a shot. I'll let you know the outcome.

Yes, cassidy, I'd like any help I can get. Thanks!

Pyrrhonist, the issue occurs with Oracle 9i (and, I'm told, higher.) Oracle 8i works with Microsoft MDAC. Thanks for the link. It's next on my reading list :-) As I said earlier, we also tried to use Oracle 9's client on a 2000 server. That failed with the same errors as the 9 client on 2003...

Well I seem to have found an answer and it isn't pretty. It seems that Microsoft's MDAC is level 2 compliant whereas Oracle 9i is level 3... they aren't compatible and there's no fix. My DBA tells me I have to use MS 2000 and Oracle 8i for ODBC compatibility. We even tried to load 9i on 2000...

Yes! I've used NetMeeting to connect to the new server. From there, I started an Oracle SQL session without a problem. I'm inclined to agree with you assessment of DBA's. They tend to live in a different world and look down on everyone else. That attitude I don't understand. Thanks for you time...

Thanks for the reply Chopstik! Love that handle :-) I'm told by the D.B.A.'s that the Oracle Components are set up. I don't know how to valid if they are; and I'm still getting the error.

I have a valid page on server that I'm moving to a new server. Loading this page from on my old serer works beautifully. However, opening the same page from the NEW server produces an error: BJC Change Management-Test Microsoft OLE DB Provider for Oracle error '80004005' Oracle client...