Hi, everyone.
I trying to connect a SQL Server 2005 to an Access 2003 frontend. Now
in the past I have not had any trouble, but today seems to be a
different day.
Every time I go to try and open a dao.database object I get the error
"Run-Time error '3000'': Reserved error(-1038); there is no message
for this error."
I am not really sure what the issue is here. Below is the line of code
Set dbSQLServer = DBEngine.OpenDatabase("", dbDriverNoPrompt, False,
gSQLServConnectionString)
Just so everything is clear gSQLServConnectionString =
ODBC;DSN=SQLServer;Trusted_Connection=ye
s;DATABASE=DicomSQLServer;
Now, I have tried a simlar connection string and it works just fine for
another server. When I test the connection in the ODBC manager it
connects to the server with a problem, but when I try to get access to
do it. I get the aforementioned error.
Thanks for all your help .
-ThanasYou may get an better response from:
microsoft.public.access.adp.sqlserver
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"Thanas" <atsioplakis@.gmail.com> wrote in message
news:1156275843.206425.221240@.i42g2000cwa.googlegroups.com...
> Hi, everyone.
> I trying to connect a SQL Server 2005 to an Access 2003 frontend. Now
> in the past I have not had any trouble, but today seems to be a
> different day.
> Every time I go to try and open a dao.database object I get the error
> "Run-Time error '3000'': Reserved error(-1038); there is no message
> for this error."
> I am not really sure what the issue is here. Below is the line of code
> Set dbSQLServer = DBEngine.OpenDatabase("", dbDriverNoPrompt, False,
> gSQLServConnectionString)
> Just so everything is clear gSQLServConnectionString =
> ODBC;DSN=SQLServer;Trusted_Connection=ye
s;DATABASE=DicomSQLServer;
> Now, I have tried a simlar connection string and it works just fine for
> another server. When I test the connection in the ODBC manager it
> connects to the server with a problem, but when I try to get access to
> do it. I get the aforementioned error.
> Thanks for all your help .
> -Thanas
>|||Thanks I'll give it a try.
Arnie Rowland wrote:[vbcol=seagreen]
> You may get an better response from:
> microsoft.public.access.adp.sqlserver
> --
> Arnie Rowland, Ph.D.
> Westwood Consulting, Inc
> Most good judgment comes from experience.
> Most experience comes from bad judgment.
> - Anonymous
>
> "Thanas" <atsioplakis@.gmail.com> wrote in message
> news:1156275843.206425.221240@.i42g2000cwa.googlegroups.com...
Showing posts with label frontend. Show all posts
Showing posts with label frontend. Show all posts
Wednesday, March 28, 2012
Problem with SQL Server And Access 2003
Hi, everyone.
I trying to connect a SQL Server 2005 to an Access 2003 frontend. Now
in the past I have not had any trouble, but today seems to be a
different day.
Every time I go to try and open a dao.database object I get the error
"Run-Time error '3000'': Reserved error(-1038); there is no message
for this error."
I am not really sure what the issue is here. Below is the line of code
Set dbSQLServer = DBEngine.OpenDatabase("", dbDriverNoPrompt, False,
gSQLServConnectionString)
Just so everything is clear gSQLServConnectionString = ODBC;DSN=SQLServer;Trusted_Connection=yes;DATABASE=DicomSQLServer;
Now, I have tried a simlar connection string and it works just fine for
another server. When I test the connection in the ODBC manager it
connects to the server with a problem, but when I try to get access to
do it. I get the aforementioned error.
Thanks for all your help .
-ThanasYou may get an better response from:
microsoft.public.access.adp.sqlserver
--
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"Thanas" <atsioplakis@.gmail.com> wrote in message
news:1156275843.206425.221240@.i42g2000cwa.googlegroups.com...
> Hi, everyone.
> I trying to connect a SQL Server 2005 to an Access 2003 frontend. Now
> in the past I have not had any trouble, but today seems to be a
> different day.
> Every time I go to try and open a dao.database object I get the error
> "Run-Time error '3000'': Reserved error(-1038); there is no message
> for this error."
> I am not really sure what the issue is here. Below is the line of code
> Set dbSQLServer = DBEngine.OpenDatabase("", dbDriverNoPrompt, False,
> gSQLServConnectionString)
> Just so everything is clear gSQLServConnectionString => ODBC;DSN=SQLServer;Trusted_Connection=yes;DATABASE=DicomSQLServer;
> Now, I have tried a simlar connection string and it works just fine for
> another server. When I test the connection in the ODBC manager it
> connects to the server with a problem, but when I try to get access to
> do it. I get the aforementioned error.
> Thanks for all your help .
> -Thanas
>|||Thanks I'll give it a try.
Arnie Rowland wrote:
> You may get an better response from:
> microsoft.public.access.adp.sqlserver
> --
> Arnie Rowland, Ph.D.
> Westwood Consulting, Inc
> Most good judgment comes from experience.
> Most experience comes from bad judgment.
> - Anonymous
>
> "Thanas" <atsioplakis@.gmail.com> wrote in message
> news:1156275843.206425.221240@.i42g2000cwa.googlegroups.com...
> > Hi, everyone.
> > I trying to connect a SQL Server 2005 to an Access 2003 frontend. Now
> > in the past I have not had any trouble, but today seems to be a
> > different day.
> >
> > Every time I go to try and open a dao.database object I get the error
> > "Run-Time error '3000'': Reserved error(-1038); there is no message
> > for this error."
> >
> > I am not really sure what the issue is here. Below is the line of code
> >
> > Set dbSQLServer = DBEngine.OpenDatabase("", dbDriverNoPrompt, False,
> > gSQLServConnectionString)
> >
> > Just so everything is clear gSQLServConnectionString => > ODBC;DSN=SQLServer;Trusted_Connection=yes;DATABASE=DicomSQLServer;
> >
> > Now, I have tried a simlar connection string and it works just fine for
> > another server. When I test the connection in the ODBC manager it
> > connects to the server with a problem, but when I try to get access to
> > do it. I get the aforementioned error.
> >
> > Thanks for all your help .
> >
> > -Thanas
> >
I trying to connect a SQL Server 2005 to an Access 2003 frontend. Now
in the past I have not had any trouble, but today seems to be a
different day.
Every time I go to try and open a dao.database object I get the error
"Run-Time error '3000'': Reserved error(-1038); there is no message
for this error."
I am not really sure what the issue is here. Below is the line of code
Set dbSQLServer = DBEngine.OpenDatabase("", dbDriverNoPrompt, False,
gSQLServConnectionString)
Just so everything is clear gSQLServConnectionString = ODBC;DSN=SQLServer;Trusted_Connection=yes;DATABASE=DicomSQLServer;
Now, I have tried a simlar connection string and it works just fine for
another server. When I test the connection in the ODBC manager it
connects to the server with a problem, but when I try to get access to
do it. I get the aforementioned error.
Thanks for all your help .
-ThanasYou may get an better response from:
microsoft.public.access.adp.sqlserver
--
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"Thanas" <atsioplakis@.gmail.com> wrote in message
news:1156275843.206425.221240@.i42g2000cwa.googlegroups.com...
> Hi, everyone.
> I trying to connect a SQL Server 2005 to an Access 2003 frontend. Now
> in the past I have not had any trouble, but today seems to be a
> different day.
> Every time I go to try and open a dao.database object I get the error
> "Run-Time error '3000'': Reserved error(-1038); there is no message
> for this error."
> I am not really sure what the issue is here. Below is the line of code
> Set dbSQLServer = DBEngine.OpenDatabase("", dbDriverNoPrompt, False,
> gSQLServConnectionString)
> Just so everything is clear gSQLServConnectionString => ODBC;DSN=SQLServer;Trusted_Connection=yes;DATABASE=DicomSQLServer;
> Now, I have tried a simlar connection string and it works just fine for
> another server. When I test the connection in the ODBC manager it
> connects to the server with a problem, but when I try to get access to
> do it. I get the aforementioned error.
> Thanks for all your help .
> -Thanas
>|||Thanks I'll give it a try.
Arnie Rowland wrote:
> You may get an better response from:
> microsoft.public.access.adp.sqlserver
> --
> Arnie Rowland, Ph.D.
> Westwood Consulting, Inc
> Most good judgment comes from experience.
> Most experience comes from bad judgment.
> - Anonymous
>
> "Thanas" <atsioplakis@.gmail.com> wrote in message
> news:1156275843.206425.221240@.i42g2000cwa.googlegroups.com...
> > Hi, everyone.
> > I trying to connect a SQL Server 2005 to an Access 2003 frontend. Now
> > in the past I have not had any trouble, but today seems to be a
> > different day.
> >
> > Every time I go to try and open a dao.database object I get the error
> > "Run-Time error '3000'': Reserved error(-1038); there is no message
> > for this error."
> >
> > I am not really sure what the issue is here. Below is the line of code
> >
> > Set dbSQLServer = DBEngine.OpenDatabase("", dbDriverNoPrompt, False,
> > gSQLServConnectionString)
> >
> > Just so everything is clear gSQLServConnectionString => > ODBC;DSN=SQLServer;Trusted_Connection=yes;DATABASE=DicomSQLServer;
> >
> > Now, I have tried a simlar connection string and it works just fine for
> > another server. When I test the connection in the ODBC manager it
> > connects to the server with a problem, but when I try to get access to
> > do it. I get the aforementioned error.
> >
> > Thanks for all your help .
> >
> > -Thanas
> >
Wednesday, March 21, 2012
Problem with simplified chinese
I have a 3 layer system, SQL Server 2000 database, COM+ dll's (VC++ 6) and
ASP frontend, this system has been in production for quite some time using
english, spanish and portuguese versions. Now I've been asked to test the
system to function with Simplified chinese. The development of the system
was outsourced and we don't have communication with the company (some sort
of legal problems i think).
Now, I've been reviewing the code and recompiled one of the core DLL's for
unicode support with no problems, I've tested the database (SQL Server 2000)
inserting Simplified Chinese characters and the DB supports it fine (the DB
fields are NVARCHAR), in the ASP frontend, the retrievel process (calling
the COM+ DLL functions) works fine displaying this data I inserted directly
in the DB.
However, when I try inserting this data through the ASP frontend I'm getting
errors regarding the length of the strings, I'm testing the data insertion
in a field limited to 100 characters, the data I'm testing are 23 Simplified
Chinese symbols or characters and when I insert them directly in the DB
there is no problem, the DB correctly interprets the string as 23 characters
long, but when I test the length of the same string on the ASP page it says
its 183 characters long, so I'm guessing the ASP code is doing some kind of
implicit conversion, I already tried setting the asp session codepage to
65001 for unicode support with the same outcome. Any ideas or tips?
Sorry for the long post, I would reaaly appreciate any kind of help.
David
David A. Caballero J. wrote:
> Sorry for the long post, I would reaaly appreciate any kind of help.
> David
I have a PDF we devised for clients who want to run our ASP package in
Chinese (unicode) - I think it deals with some of the issues you've come
across. Let me know if I can send it to your hotmail address (I'm
assuming it's genuine) and I'll send it over.
The reason you are seeing more characters is because the chars are
displayed in web page HTML source as numerical codes made up of ASCII chars.
captain_flackTONYBLAIRFROMOFFICE@.hotmail.com
(remove Tony Blair from office to contact me)
ASP frontend, this system has been in production for quite some time using
english, spanish and portuguese versions. Now I've been asked to test the
system to function with Simplified chinese. The development of the system
was outsourced and we don't have communication with the company (some sort
of legal problems i think).
Now, I've been reviewing the code and recompiled one of the core DLL's for
unicode support with no problems, I've tested the database (SQL Server 2000)
inserting Simplified Chinese characters and the DB supports it fine (the DB
fields are NVARCHAR), in the ASP frontend, the retrievel process (calling
the COM+ DLL functions) works fine displaying this data I inserted directly
in the DB.
However, when I try inserting this data through the ASP frontend I'm getting
errors regarding the length of the strings, I'm testing the data insertion
in a field limited to 100 characters, the data I'm testing are 23 Simplified
Chinese symbols or characters and when I insert them directly in the DB
there is no problem, the DB correctly interprets the string as 23 characters
long, but when I test the length of the same string on the ASP page it says
its 183 characters long, so I'm guessing the ASP code is doing some kind of
implicit conversion, I already tried setting the asp session codepage to
65001 for unicode support with the same outcome. Any ideas or tips?
Sorry for the long post, I would reaaly appreciate any kind of help.
David
David A. Caballero J. wrote:
> Sorry for the long post, I would reaaly appreciate any kind of help.
> David
I have a PDF we devised for clients who want to run our ASP package in
Chinese (unicode) - I think it deals with some of the issues you've come
across. Let me know if I can send it to your hotmail address (I'm
assuming it's genuine) and I'll send it over.
The reason you are seeing more characters is because the chars are
displayed in web page HTML source as numerical codes made up of ASCII chars.
captain_flackTONYBLAIRFROMOFFICE@.hotmail.com
(remove Tony Blair from office to contact me)
Subscribe to:
Posts (Atom)