Some old c++ programm are connecting to the sql server,
but they don't work after the migration to 2000 is done.
Here is an example of an error:
Catch exception at this line in the c++ programm:
PointeurProduitSet->Open(CRecordset::dynaset, strSQL,
CRecordset::none);
Yumg.exe has generated an error and will be closed..
The "scripting code page" suggested during upgrade is
1252, Is it possible that there is another code setting
in the sl6.5 server?This is a multi-part message in MIME format.
--=_NextPart_000_007C_01C35CC3.B987AAC0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Have you upgraded your client machines? Use your SQL Server 2000 CD to =install the Client Connectivity (MDAC) DLL's.
-- Tom
---
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinnaclepublishing.com/sql
"Jean-Francois Bouchard" <jeanfrancois_21@.hotmail.com> wrote in message =news:0a8d01c35ce2$85e07570$a501280a@.phx.gbl...
I'm migrating sql 6.5 to 2000 on a test environnement.
Some old c++ programm are connecting to the sql server, but they don't work after the migration to 2000 is done. Here is an example of an error:
Catch exception at this line in the c++ programm:
PointeurProduitSet->Open(CRecordset::dynaset, strSQL, CRecordset::none);
Yumg.exe has generated an error and will be closed..
The "scripting code page" suggested during upgrade is 1252, Is it possible that there is another code setting in the sl6.5 server?
--=_NextPart_000_007C_01C35CC3.B987AAC0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&
Have you upgraded your client =machines? Use your SQL Server 2000 CD to install the Client Connectivity (MDAC) DLL's.
-- Tom
---T=homas A. Moreau, BSc, PhD, MCSE, MCDBASQL Server MVPColumnist, SQL =Server ProfessionalToronto, ON Canadahttp://www.pinnaclepublishing.com/sql">www.pinnaclepublishing.com=/sql
"Jean-Francois Bouchard"
--=_NextPart_000_007C_01C35CC3.B987AAC0--|||I did try many things in the past like installing
different version of MDAC 2.5 and 2.7..
Right now I just installed IE5 & sql 2000 connectivity
tools from the sql server 2000 cd.. and it's not working
I get the same error as usual..
any other suggestion ?
>--Original Message--
>Have you upgraded your client machines? Use your SQL
Server 2000 CD to install the Client Connectivity (MDAC)
DLL's.
>--
>Tom
>----
--
>Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
>SQL Server MVP
>Columnist, SQL Server Professional
>Toronto, ON Canada
>www.pinnaclepublishing.com/sql
>
>"Jean-Francois Bouchard" <jeanfrancois_21@.hotmail.com>
wrote in message news:0a8d01c35ce2$85e07570
$a501280a@.phx.gbl...
>I'm migrating sql 6.5 to 2000 on a test environnement.
>Some old c++ programm are connecting to the sql server,
>but they don't work after the migration to 2000 is
done.
>Here is an example of an error:
>Catch exception at this line in the c++ programm:
>PointeurProduitSet->Open(CRecordset::dynaset, strSQL,
>CRecordset::none);
>Yumg.exe has generated an error and will be closed..
>The "scripting code page" suggested during upgrade is
>1252, Is it possible that there is another code setting
>in the sl6.5 server?
>|||This is a multi-part message in MIME format.
--=_NextPart_000_001A_01C35D0C.48ABB870
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Not sure if the latest SP for SQL 2000 would help.
-- Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinnaclepublishing.com/sql
.
"Jean-Francois Bouchard" <jeanfrancois_21@.hotmail.com> wrote in message =news:0b5801c35ceb$ed5cd5a0$a401280a@.phx.gbl...
I did try many things in the past like installing different version of MDAC 2.5 and 2.7..
Right now I just installed IE5 & sql 2000 connectivity tools from the sql server 2000 cd.. and it's not working I get the same error as usual..
any other suggestion ?
>--Original Message--
>Have you upgraded your client machines? Use your SQL Server 2000 CD to install the Client Connectivity (MDAC) DLL's.
>-- >Tom
>----
--
>Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
>SQL Server MVP
>Columnist, SQL Server Professional
>Toronto, ON Canada
>www.pinnaclepublishing.com/sql
>
>"Jean-Francois Bouchard" <jeanfrancois_21@.hotmail.com> wrote in message news:0a8d01c35ce2$85e07570
$a501280a@.phx.gbl...
>I'm migrating sql 6.5 to 2000 on a test environnement. >Some old c++ programm are connecting to the sql server, >but they don't work after the migration to 2000 is done. >Here is an example of an error:
>Catch exception at this line in the c++ programm:
>PointeurProduitSet->Open(CRecordset::dynaset, strSQL, >CRecordset::none);
>Yumg.exe has generated an error and will be closed..
>The "scripting code page" suggested during upgrade is >1252, Is it possible that there is another code setting >in the sl6.5 server?
>
--=_NextPart_000_001A_01C35D0C.48ABB870
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&
Not sure if the latest SP for SQL 2000 =would help.
-- Tom
----Thomas A. =Moreau, BSc, PhD, MCSE, MCDBASQL Server MVPColumnist, SQL Server ProfessionalToronto, ON Canadahttp://www.pinnaclepublishing.com/sql">www.pinnaclepublishing.com=/sql.
"Jean-Francois Bouchard"
--=_NextPart_000_001A_01C35D0C.48ABB870--|||Jean-Francois Bouchard (jeanfrancois_21@.hotmail.com) writes:
> I'm migrating sql 6.5 to 2000 on a test environnement.
> Some old c++ programm are connecting to the sql server,
> but they don't work after the migration to 2000 is done.
> Here is an example of an error:
> Catch exception at this line in the c++ programm:
> PointeurProduitSet->Open(CRecordset::dynaset, strSQL,
> CRecordset::none);
> Yumg.exe has generated an error and will be closed..
> The "scripting code page" suggested during upgrade is
> 1252, Is it possible that there is another code setting
> in the sl6.5 server?
It is not liklely you would get exceptions due to code-page problem. But
to review the setting on 6.5, use sp_helpsort.
What client library does the C++ programs use?
I'm afraid that you will have to debug your programs to get more
detailed information about where things go wrong.
--
Erland Sommarskog, SQL Server MVP, sommar@.algonet.se
Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techinfo/productdoc/2000/books.asp|||After debugging the c++ application, I see that the
faulty line is this one:
try
{
PointeurSecuriteSet->Open
(CRecordset::dynaset, "{call sp_SelectSecurite()}",
CRecordset::none);
}
catch (CDBException *e)
The Open is failed, so it goes to the catch exception
part..
The connection to sql server is established through ODBC..
These properties are setted up before calling the open:
PointeurSecuriteSet = new (CSecuriteSet);
PointeurSecuriteSet->m_NomDsn = m_NomDsn;
PointeurSecuriteSet->m_NomUid = m_NomUid;
PointeurSecuriteSet->m_NomPwd = m_NomPwd;
I did try to trace what's happening via SQL trace, but I
didn't see the call of the stored proc
sp_selectsecurite.. any other things I can do to get it
working?
Thanks for your help!
>--Original Message--
>Jean-Francois Bouchard (jeanfrancois_21@.hotmail.com)
writes:
>> I'm migrating sql 6.5 to 2000 on a test
environnement.
>> Some old c++ programm are connecting to the sql
server,
>> but they don't work after the migration to 2000 is
done.
>> Here is an example of an error:
>> Catch exception at this line in the c++ programm:
>> PointeurProduitSet->Open(CRecordset::dynaset, strSQL,
>> CRecordset::none);
>> Yumg.exe has generated an error and will be closed..
>> The "scripting code page" suggested during upgrade is
>> 1252, Is it possible that there is another code
setting
>> in the sl6.5 server?
>It is not liklely you would get exceptions due to code-
page problem. But
>to review the setting on 6.5, use sp_helpsort.
>What client library does the C++ programs use?
>I'm afraid that you will have to debug your programs to
get more
>detailed information about where things go wrong.
>--
>Erland Sommarskog, SQL Server MVP, sommar@.algonet.se
>Books Online for SQL Server SP3 at
>http://www.microsoft.com/sql/techinfo/productdoc/2000/boo
ks.asp
>.
>|||The c++ programm was not working because the call to a
stored procedure in SQL 2000 must be without () if you
don't have parameters.
sp_SelectSecurite() must be :
sp_SelectSecurite
It's working well now.
Thanks guys
>--Original Message--
>I'm migrating sql 6.5 to 2000 on a test environnement.
>Some old c++ programm are connecting to the sql server,
>but they don't work after the migration to 2000 is
done.
>Here is an example of an error:
>Catch exception at this line in the c++ programm:
>PointeurProduitSet->Open(CRecordset::dynaset, strSQL,
>CRecordset::none);
>Yumg.exe has generated an error and will be closed..
>The "scripting code page" suggested during upgrade is
>1252, Is it possible that there is another code setting
>in the sl6.5 server?
>.
>|||Jean-Francois Bouchard (jeanfrancois_21@.hotmail.com) writes:
> After debugging the c++ application, I see that the
> faulty line is this one:
> try
> {
> PointeurSecuriteSet->Open
> (CRecordset::dynaset, "{call sp_SelectSecurite()}",
> CRecordset::none);
> }
> catch (CDBException *e)
> The Open is failed, so it goes to the catch exception
> part..
> The connection to sql server is established through ODBC..
> These properties are setted up before calling the open:
> PointeurSecuriteSet = new (CSecuriteSet);
> PointeurSecuriteSet->m_NomDsn = m_NomDsn;
> PointeurSecuriteSet->m_NomUid = m_NomUid;
> PointeurSecuriteSet->m_NomPwd = m_NomPwd;
> I did try to trace what's happening via SQL trace, but I
> didn't see the call of the stored proc
> sp_selectsecurite.. any other things I can do to get it
> working?
Does the exception come with any error message?
Since you don't see the call, it may be that things go wrong before
the call is issued.
Does the stored procedure run OK if you run it from Query Analyzer.
A general piece advice which is not likely to resolve this issue is
not use sp_ as the first letters in your procedure names. This prefix
is reserved for system procedure and SQL Server first looks in master
for these.
--
Erland Sommarskog, SQL Server MVP, sommar@.algonet.se
Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techinfo/productdoc/2000/books.asp
No comments:
Post a Comment