Client of mine has Arev 2.1, MSSQL bond running fine against an NT 3.51 box with SQL 4.21 (Microsoft). we want to move the app and the SQL to MSSQL 6.5 and continue to use DBNMPIPE. Does this work or am I wasting my time. Any help will save me from execution.

The last version of SQL I worked with (6.0) still came supplied with DBNMPIPE, so I presume this would work with your SQL bond, but I can't vouch from experience.

In the times I have been watching this forum, I have noticed that those few posts that mention the AREV SQL bond generally go unanswered. I gather that the silence from RevSoft is a marketing decision, after all SQL competes with the LH NLM and NT service. From everyone else, I assume that the SQL Bond just isn't used much.

On Microsoft's side, they are well on their way to obsoleting DOS (imho - just take a look at http://www.microsoft.com/support/supportnet/suppobsolescence.asp), so it is getting increasingly hard to get info to solve the problems you may encounter.

If the NT3.51/SQL 4.21 installation works, why change it?

I would venture to say that if they have Sql Bond working then as long as the continue to use the same 16bit drivers from MS they should be able to upgrade to Nt4 and Server 6.5 without a problem.

They are the same drivers we have to use in OpenInsight.

dsig

David Tod Sigafoos ~ SigSolutions

[email protected] voice: 503-639-8080 cis:70302,77

NOTICE FOR RTI FORUMS: The message above is an answer to a user request and should

be taken as personal opinion only.

Although care was taken to not hurt anyones feelings or impugn the quality of any product, support or idea IF there is an

exception taken please note in detail the offending portion of the note and email me. I will take all notes under advisement.

We are currently and successfully using SQL Server 6.5 with NT Server 4.1. As long as you use only MSSQL_C calls in your code, it should

convert with no required changes.

As a note the system here also requires us to use DBMSSPX.EXE and

some beta kludge called DATASEG.EXE. The combination eats up another

70+k of precious memory. There have been posts from people claiming to have gotten around this, but I have yet to obtain any docs explaining how to achieve this.

I have an AREV 2.1 app and SQL Server 1.1… using AREV last SQL Server bond… I wanted to upgrade to 6.5, but all I could ever find out was that I couldn't without going to OI… Just wanted to verify that we're all talking about the same thing here??? If so, can someone who has this working leave an email address or phone numer so I can find out exactly how to set this up??

Thanks so much…

Karen Layton

[email protected]

View this thread on the forum...