Friday, March 30, 2012
RunSQL method with tables linked to SQL2005 Express
1. The DoCmd.RunSQL method works fine with tables linked (ODBC) to SQL 2000
on a first machine. On this machine, SQL2005 is not installed.
2. On a second machine, with SQL2000 and SQL2005Express installed,
DoCmd.RunSQL fails with tables linked to SQL2000 or SQL2005Express. In both
cases, I get error '3024' 'File C:\Documents and Settings\ ... \dbo.mdb not
found'.
I checked SQL2005 configuration with the SQL2005 configuration tools, and it
seems ok.
Apart from the RunSQL method, the linked tables can be accessed normally.
Any idea ? Thanks in advance.
Hi,
My understanding of your issue is that:
Your Acess application failed with tables linked to SQL Server 2000 or SQL
2005 Express. The error was '3024' 'File C:\Documents and Settings\ ...
\dbo.mdb not
found'.
If I have misunderstood, please let me know.
I performed a test but unfortunately I didn't reproduce your issue. My test
was based on the following steps:
1. Create an Access database in Acess 2003
2. Create a SQL Server 2000 database to the File DSN
4. Add linked tables from the ODBC File DSN
5. Create a Form in Acess 2003
6. Add code in the click event:
Dim strSQL As String
strSQL = "Update dbo_Products SET ProductName='" & Me.Text1.Text & "'
where ProductID=" & Me.comProductId
DoCmd.RunSQL strSQL
MsgBox "OK"
7. Save the database
Firstly, I opened the database file and triggered the click event of the
Form on my local computer with SQL Server 2000 and SQL Server 2005 without
any problem, then I copied the .mdb file to another machine with SQL Server
2000 and SQL Server 2005 Express, ran it again, and it also worked fine.
From your error message, it seems that your dbo.mdb file cannot be found.
Please check that.
Also, could you please tell me more detailed on your scenario? It is better
that you could describe your whole process so that I could better
understand your issue and probably reproduce your issue according to your
steps.
If you have any other questions or concerns, please feel free to let me
know. It's my pleasure to be of assistance.
Charles Wang
Microsoft Online Community Support
================================================== ====
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
================================================== ====
This posting is provided "AS IS" with no warranties, and confers no rights.
================================================== ====
|||Charles,
Thanks for your testing and fast reply.
Your scenario is quite similar to mine and I can't see why results are
different.
In fact, it looks like if access to the tables concerned is denied. So I am
suspecting SQL 2005 security. Before going further in tests, I will have a
closer look at SQL 2005 schemas, which I am new in as they did not exist in
SQL 2000.
When I have completed this, I will let you know more.
Thanks to you.
"Charles Wang[MSFT]" wrote:
> Hi,
> My understanding of your issue is that:
> Your Acess application failed with tables linked to SQL Server 2000 or SQL
> 2005 Express. The error was '3024' 'File C:\Documents and Settings\ ...
> \dbo.mdb not
> found'.
> If I have misunderstood, please let me know.
> I performed a test but unfortunately I didn't reproduce your issue. My test
> was based on the following steps:
> 1. Create an Access database in Acess 2003
> 2. Create a SQL Server 2000 database to the File DSN
> 4. Add linked tables from the ODBC File DSN
> 5. Create a Form in Acess 2003
> 6. Add code in the click event:
> Dim strSQL As String
> strSQL = "Update dbo_Products SET ProductName='" & Me.Text1.Text & "'
> where ProductID=" & Me.comProductId
> DoCmd.RunSQL strSQL
> MsgBox "OK"
> 7. Save the database
> Firstly, I opened the database file and triggered the click event of the
> Form on my local computer with SQL Server 2000 and SQL Server 2005 without
> any problem, then I copied the .mdb file to another machine with SQL Server
> 2000 and SQL Server 2005 Express, ran it again, and it also worked fine.
> From your error message, it seems that your dbo.mdb file cannot be found.
> Please check that.
> Also, could you please tell me more detailed on your scenario? It is better
> that you could describe your whole process so that I could better
> understand your issue and probably reproduce your issue according to your
> steps.
> If you have any other questions or concerns, please feel free to let me
> know. It's my pleasure to be of assistance.
> Charles Wang
> Microsoft Online Community Support
> ================================================== ====
> When responding to posts, please "Reply to Group" via
> your newsreader so that others may learn and benefit
> from this issue.
> ================================================== ====
> This posting is provided "AS IS" with no warranties, and confers no rights.
> ================================================== ====
>
>
|||Charles,
Finally, I got it. The issue is this :
1. When, in ACCESS, you create a link to a SQL table which hasn't got a
primary key, a dialog box appears in second, asking for a field unique
identifier. If you do not select a field, the link is however created and you
can access normally to the table from ACCESS. But the Docmd.RunSql method
does not work. What is disturbing in that case is that the table link is
created however.
2. On another hand, if you select a unique identifier while the source table
hasn't got any primary key, it leads to incoherent behaviour such as tables
appearing different in ACCESS from their real content in SQL.
3. My conclusion is : If you have source tables without primary key (which
of course can happen), you have to choose between A/ Not using Docmd.RunSql
(or CurrentDb.Execute) or B/ Having dangerous behaviour in your app.
I would say it sounds more or less buggy.
I think you will understand my pain when I say it is a real waste that
Microsoft is abandonning ADP platform. With ADPs you can directly manipulate
SQL objects in ACCESS, such as tables, views, procs, ... (and what is more:
most often without writing any code). And this trouble could not happen.
I would be very glad to know your feeling about all this.
Once more, many thanks for your help.
"Charles Wang[MSFT]" wrote:
> Hi,
> My understanding of your issue is that:
> Your Acess application failed with tables linked to SQL Server 2000 or SQL
> 2005 Express. The error was '3024' 'File C:\Documents and Settings\ ...
> \dbo.mdb not
> found'.
> If I have misunderstood, please let me know.
> I performed a test but unfortunately I didn't reproduce your issue. My test
> was based on the following steps:
> 1. Create an Access database in Acess 2003
> 2. Create a SQL Server 2000 database to the File DSN
> 4. Add linked tables from the ODBC File DSN
> 5. Create a Form in Acess 2003
> 6. Add code in the click event:
> Dim strSQL As String
> strSQL = "Update dbo_Products SET ProductName='" & Me.Text1.Text & "'
> where ProductID=" & Me.comProductId
> DoCmd.RunSQL strSQL
> MsgBox "OK"
> 7. Save the database
> Firstly, I opened the database file and triggered the click event of the
> Form on my local computer with SQL Server 2000 and SQL Server 2005 without
> any problem, then I copied the .mdb file to another machine with SQL Server
> 2000 and SQL Server 2005 Express, ran it again, and it also worked fine.
> From your error message, it seems that your dbo.mdb file cannot be found.
> Please check that.
> Also, could you please tell me more detailed on your scenario? It is better
> that you could describe your whole process so that I could better
> understand your issue and probably reproduce your issue according to your
> steps.
> If you have any other questions or concerns, please feel free to let me
> know. It's my pleasure to be of assistance.
> Charles Wang
> Microsoft Online Community Support
> ================================================== ====
> When responding to posts, please "Reply to Group" via
> your newsreader so that others may learn and benefit
> from this issue.
> ================================================== ====
> This posting is provided "AS IS" with no warranties, and confers no rights.
> ================================================== ====
>
>
|||Hi Jason,
Thanks for your detailed explanation on this issue which make me totally
understand your issue.
Yes, I reproduced your issue according to your steps. It is indeed an by
design issue.
Please refer to:
276035PRB: ADOX Creates Read Only Linked Tables to Access Databases
http://support.microsoft.com/default...b;EN-US;276035
If you are very concerned on this issue, I recommend that you give
Microsoft feedback which will be routed to the related team via the link:
http://www.microsoft.com/office/comm...pe=suggestion&
lang=en&cr=US&cat=en-us-office&pt=3a4e9862-cdce-4bdc-8664-91038e3eb1e9
Also, ADP is still available in Access 2007
http://technet2.microsoft.com/Office...1c-446a-8ff2-2
21769a58ba51033.mspx?mfr=true
For now, you may assign the primary key in your Access database file when
you add the linked table due to no better alternative resolutions on this
issue.
If you have any other questions or concerns, please feel free to let me
know. It's my pleasure to be of assistance.
Charles Wang
Microsoft Online Community Support
================================================== ====
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
================================================== ====
This posting is provided "AS IS" with no warranties, and confers no rights.
================================================== ====
|||Charles,
Thanks for your reply. Just one comment about your suggestion of assigning a
field unique identifier to a link, while source table hasn't got a primary
key.
1. Let us consider a SQL table with no primary key :
empl_Name empl_FirstName
-- --
BROWN Bob
COPPERFIELD Jim
TAYLOR Evans
BROWN Mary
2. In ACCESS (.mdb), create an odbc link to this table, selecting empl_Name
as unique identifier. The link is created without any warning.
3. Then, you can have a look at your table in ACCESS. You will see :
empl_Name empl_FirstName
-- --
BROWN Bob
COPPERFIELD Jim
TAYLOR Evans
BROWN Bob
A bit confusing ...
|||Hi Jason,
Thanks for your detailed response.
In this case, you can choose the two columns empl_Name and empl_FirstName
as the unique record identifier.
Please feel free to let me know if you have any other questions or
concerns.
Have a great day!
Charles Wang
Microsoft Online Community Support
================================================== ====
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
================================================== ====
This posting is provided "AS IS" with no warranties, and confers no rights.
================================================== ====
|||Hi,
I am interested in this issue. Would you mind letting me know the result of
the suggestions? If you need further assistance, feel free to let me know.
I will be more than happy to be of assistance.
Have a great day!
Charles Wang
Microsoft Online Community Support
|||Charles,
Thanks very much for your interest in my issue.
My context is the following :
1. I have been developing for long with ADPs, doing the "hard job" in SQL
Server, and using ACCESS as front end. I considered this way of doing as
highly productive. My field could be described as the construction of
analytical relational databases fed with data coming from transactional
systems (finance, supply chain, ... ).
2. Unfortunately, Microsoft is leaving ADP platform. As a matter of fact,
you will see ADPs in ACCESS 2007, but just for the purpose of compatibility.
From now, ADPs don't work with SQL 2005 as far as building purpose is
concerned.
3. So, I am going back to ODBC and ADO with ACCESS .mdb. And problems come.
The one I met with DoCmd.RunSql (or CurrentDb.execute) is one amongst many.
For instance, links refreshing is quite an issue. If you have to frequently
create/kill tables in SQL Server, links management gets complicated.
Thanks for your suggestion, about my example, of selecting two fields as
unique identifier. I confess I didn't think of it. But the problem is
elsewhere : when you receive, from transactional systems, data in tables with
no primary key (and this frequently happens), it would not be reasonable to
add a unique identifier when creating odbc link, as you may never be sure
about the existence of duplicates.
With ADPs, everything is more simple : you work with the database "as it
is", without interfering with risky adds. Roughly speaking, "what you see is
what you get". And of course the direct manipulation of SQL objects in
ACCESS, with no code writing, allows fast developments.
4. As a conclusion, I would say it is possible to find a solution, more or
less satisfying, to this RunSQL problem (In fact, the definite solution will
be to avoid this method). But the real fact is that there is galaxy between
ADPs and ODBC/ADO (in ACCESS world of course) ...
What is rather strange is that Microsoft has, for years, presented ADPs as
THE solution for client/server ACCESS apps.
Once again, thanks very much for your help and interest in these questions.
"Charles Wang[MSFT]" wrote:
> Hi,
> I am interested in this issue. Would you mind letting me know the result of
> the suggestions? If you need further assistance, feel free to let me know.
> I will be more than happy to be of assistance.
> Have a great day!
> Charles Wang
> Microsoft Online Community Support
>
|||Hi Jason,
Appreciate your detailed response. I do understand your concerns. Just one
point that you mentioned I cannot understand clearly.
You said, "From now, ADPs don't work with SQL 2005 as far as building
purpose is concerned.". Did you mean that ADPs cannot work with SQL 2005
from now on? As far as I know, both Access 2003 and Access 2007 can work
well with SQL 2005 Express, Standard and Enterprise edtions.
Did you encounter some issue when you use ADP to work with SQL 2005? If so,
please post the issue here and I can assist you on it.
I performed a test with ADP and managed to update a SQL Server 2005 Express
table with primary key. Also, I managed to execute DoCmd.RunSQL on a no
primary key table in ADP:
I created a table in SQL 2005 Express:
CREATE TABLE [dbo].[Employee](
[First_Name] [varchar](50) COLLATE SQL_Latin1_General_CP1_CI_AS NOT NULL,
[Last_Name] [varchar](50) COLLATE SQL_Latin1_General_CP1_CI_AS NOT NULL,
[Description] [varchar](50) COLLATE SQL_Latin1_General_CP1_CI_AS NULL
)
INSERT INTO Employee VALUES('F1','L1','F1 L1')
INSERT INTO Employee VALUES('F2','L2','F2 L2')
INSERT INTO Employee VALUES('F1','L1','F1 L1')
Then in ADP, I managed to run the query:
DoCmd.RunSQL "Update Employee SET Description='FX LX' WHERE First_Name =
'F1'"
For a table with no primary key, I think it is a by design limitation in
Access database (.mdb) and I have submited a feedback for this.
If you have any other questions or concerns, please feel free to let me
know. It is my pleasure to be of assistance.
Charles Wang
Microsoft Online Community Support
================================================== ====
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
================================================== ====
This posting is provided "AS IS" with no warranties, and confers no rights.
================================================== ====
RunSQL method with tables linked to SQL2005 Express
1. The DoCmd.RunSQL method works fine with tables linked (ODBC) to SQL 2000
on a first machine. On this machine, SQL2005 is not installed.
2. On a second machine, with SQL2000 and SQL2005Express installed,
DoCmd.RunSQL fails with tables linked to SQL2000 or SQL2005Express. In both
cases, I get error '3024' 'File C:\Documents and Settings\ ... \dbo.mdb not
found'.
I checked SQL2005 configuration with the SQL2005 configuration tools, and it
seems ok.
Apart from the RunSQL method, the linked tables can be accessed normally.
Any idea ? Thanks in advance.Hi,
My understanding of your issue is that:
Your Acess application failed with tables linked to SQL Server 2000 or SQL
2005 Express. The error was '3024' 'File C:\Documents and Settings\ ...
\dbo.mdb not
found'.
If I have misunderstood, please let me know.
I performed a test but unfortunately I didn't reproduce your issue. My test
was based on the following steps:
1. Create an Access database in Acess 2003
2. Create a SQL Server 2000 database to the File DSN
4. Add linked tables from the ODBC File DSN
5. Create a Form in Acess 2003
6. Add code in the click event:
Dim strSQL As String
strSQL = "Update dbo_Products SET ProductName='" & Me.Text1.Text & "'
where ProductID=" & Me.comProductId
DoCmd.RunSQL strSQL
MsgBox "OK"
7. Save the database
Firstly, I opened the database file and triggered the click event of the
Form on my local computer with SQL Server 2000 and SQL Server 2005 without
any problem, then I copied the .mdb file to another machine with SQL Server
2000 and SQL Server 2005 Express, ran it again, and it also worked fine.
From your error message, it seems that your dbo.mdb file cannot be found.
Please check that.
Also, could you please tell me more detailed on your scenario? It is better
that you could describe your whole process so that I could better
understand your issue and probably reproduce your issue according to your
steps.
If you have any other questions or concerns, please feel free to let me
know. It's my pleasure to be of assistance.
Charles Wang
Microsoft Online Community Support
========================================
==============
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
========================================
==============
This posting is provided "AS IS" with no warranties, and confers no rights.
========================================
==============|||Charles,
Thanks for your testing and fast reply.
Your scenario is quite similar to mine and I can't see why results are
different.
In fact, it looks like if access to the tables concerned is denied. So I am
suspecting SQL 2005 security. Before going further in tests, I will have a
closer look at SQL 2005 schemas, which I am new in as they did not exist in
SQL 2000.
When I have completed this, I will let you know more.
Thanks to you.
"Charles Wang[MSFT]" wrote:
> Hi,
> My understanding of your issue is that:
> Your Acess application failed with tables linked to SQL Server 2000 or SQL
> 2005 Express. The error was '3024' 'File C:\Documents and Settings\ ...
> \dbo.mdb not
> found'.
> If I have misunderstood, please let me know.
> I performed a test but unfortunately I didn't reproduce your issue. My tes
t
> was based on the following steps:
> 1. Create an Access database in Acess 2003
> 2. Create a SQL Server 2000 database to the File DSN
> 4. Add linked tables from the ODBC File DSN
> 5. Create a Form in Acess 2003
> 6. Add code in the click event:
> Dim strSQL As String
> strSQL = "Update dbo_Products SET ProductName='" & Me.Text1.Text & "
'
> where ProductID=" & Me.comProductId
> DoCmd.RunSQL strSQL
> MsgBox "OK"
> 7. Save the database
> Firstly, I opened the database file and triggered the click event of the
> Form on my local computer with SQL Server 2000 and SQL Server 2005 without
> any problem, then I copied the .mdb file to another machine with SQL Serve
r
> 2000 and SQL Server 2005 Express, ran it again, and it also worked fine.
> From your error message, it seems that your dbo.mdb file cannot be found.
> Please check that.
> Also, could you please tell me more detailed on your scenario? It is bette
r
> that you could describe your whole process so that I could better
> understand your issue and probably reproduce your issue according to your
> steps.
> If you have any other questions or concerns, please feel free to let me
> know. It's my pleasure to be of assistance.
> Charles Wang
> Microsoft Online Community Support
> ========================================
==============
> When responding to posts, please "Reply to Group" via
> your newsreader so that others may learn and benefit
> from this issue.
> ========================================
==============
> This posting is provided "AS IS" with no warranties, and confers no rights
.
> ========================================
==============
>
>|||Charles,
Finally, I got it. The issue is this :
1. When, in ACCESS, you create a link to a SQL table which hasn't got a
primary key, a dialog box appears in second, asking for a field unique
identifier. If you do not select a field, the link is however created and yo
u
can access normally to the table from ACCESS. But the Docmd.RunSql method
does not work. What is disturbing in that case is that the table link is
created however.
2. On another hand, if you select a unique identifier while the source table
hasn't got any primary key, it leads to incoherent behaviour such as tables
appearing different in ACCESS from their real content in SQL.
3. My conclusion is : If you have source tables without primary key (which
of course can happen), you have to choose between A/ Not using Docmd.RunSql
(or CurrentDb.Execute) or B/ Having dangerous behaviour in your app.
I would say it sounds more or less buggy.
I think you will understand my pain when I say it is a real waste that
Microsoft is abandonning ADP platform. With ADPs you can directly manipulate
SQL objects in ACCESS, such as tables, views, procs, ... (and what is more:
most often without writing any code). And this trouble could not happen.
I would be very glad to know your feeling about all this.
Once more, many thanks for your help.
"Charles Wang[MSFT]" wrote:
> Hi,
> My understanding of your issue is that:
> Your Acess application failed with tables linked to SQL Server 2000 or SQL
> 2005 Express. The error was '3024' 'File C:\Documents and Settings\ ...
> \dbo.mdb not
> found'.
> If I have misunderstood, please let me know.
> I performed a test but unfortunately I didn't reproduce your issue. My tes
t
> was based on the following steps:
> 1. Create an Access database in Acess 2003
> 2. Create a SQL Server 2000 database to the File DSN
> 4. Add linked tables from the ODBC File DSN
> 5. Create a Form in Acess 2003
> 6. Add code in the click event:
> Dim strSQL As String
> strSQL = "Update dbo_Products SET ProductName='" & Me.Text1.Text & "
'
> where ProductID=" & Me.comProductId
> DoCmd.RunSQL strSQL
> MsgBox "OK"
> 7. Save the database
> Firstly, I opened the database file and triggered the click event of the
> Form on my local computer with SQL Server 2000 and SQL Server 2005 without
> any problem, then I copied the .mdb file to another machine with SQL Serve
r
> 2000 and SQL Server 2005 Express, ran it again, and it also worked fine.
> From your error message, it seems that your dbo.mdb file cannot be found.
> Please check that.
> Also, could you please tell me more detailed on your scenario? It is bette
r
> that you could describe your whole process so that I could better
> understand your issue and probably reproduce your issue according to your
> steps.
> If you have any other questions or concerns, please feel free to let me
> know. It's my pleasure to be of assistance.
> Charles Wang
> Microsoft Online Community Support
> ========================================
==============
> When responding to posts, please "Reply to Group" via
> your newsreader so that others may learn and benefit
> from this issue.
> ========================================
==============
> This posting is provided "AS IS" with no warranties, and confers no rights
.
> ========================================
==============
>
>|||Hi Jason,
Thanks for your detailed explanation on this issue which make me totally
understand your issue.
Yes, I reproduced your issue according to your steps. It is indeed an by
design issue.
Please refer to:
276035 PRB: ADOX Creates Read Only Linked Tables to Access Databases
http://support.microsoft.com/defaul...kb;EN-US;276035
If you are very concerned on this issue, I recommend that you give
Microsoft feedback which will be routed to the related team via the link:
http://www.microsoft.com/office/com...ype=suggestion&
lang=en&cr=US&cat=en-us-office&pt=3a4e9862-cdce-4bdc-8664-91038e3eb1e9
Also, ADP is still available in Access 2007
http://technet2.microsoft.com/Offic...a1c-446a-8ff2-2
21769a58ba51033.mspx?mfr=true
For now, you may assign the primary key in your Access database file when
you add the linked table due to no better alternative resolutions on this
issue.
If you have any other questions or concerns, please feel free to let me
know. It's my pleasure to be of assistance.
Charles Wang
Microsoft Online Community Support
========================================
==============
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
========================================
==============
This posting is provided "AS IS" with no warranties, and confers no rights.
========================================
==============|||Charles,
Thanks for your reply. Just one comment about your suggestion of assigning a
field unique identifier to a link, while source table hasn't got a primary
key.
1. Let us consider a SQL table with no primary key :
empl_Name empl_FirstName
-- --
BROWN Bob
COPPERFIELD Jim
TAYLOR Evans
BROWN Mary
2. In ACCESS (.mdb), create an odbc link to this table, selecting empl_Name
as unique identifier. The link is created without any warning.
3. Then, you can have a look at your table in ACCESS. You will see :
empl_Name empl_FirstName
-- --
BROWN Bob
COPPERFIELD Jim
TAYLOR Evans
BROWN Bob
A bit confusing ...|||Hi Jason,
Thanks for your detailed response.
In this case, you can choose the two columns empl_Name and empl_FirstName
as the unique record identifier.
Please feel free to let me know if you have any other questions or
concerns.
Have a great day!
Charles Wang
Microsoft Online Community Support
========================================
==============
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
========================================
==============
This posting is provided "AS IS" with no warranties, and confers no rights.
========================================
==============|||Hi,
I am interested in this issue. Would you mind letting me know the result of
the suggestions? If you need further assistance, feel free to let me know.
I will be more than happy to be of assistance.
Have a great day!
Charles Wang
Microsoft Online Community Support|||Charles,
Thanks very much for your interest in my issue.
My context is the following :
1. I have been developing for long with ADPs, doing the "hard job" in SQL
Server, and using ACCESS as front end. I considered this way of doing as
highly productive. My field could be described as the construction of
analytical relational databases fed with data coming from transactional
systems (finance, supply chain, ... ).
2. Unfortunately, Microsoft is leaving ADP platform. As a matter of fact,
you will see ADPs in ACCESS 2007, but just for the purpose of compatibility.
From now, ADPs don't work with SQL 2005 as far as building purpose is
concerned.
3. So, I am going back to ODBC and ADO with ACCESS .mdb. And problems come.
The one I met with DoCmd.RunSql (or CurrentDb.execute) is one amongst many.
For instance, links refreshing is quite an issue. If you have to frequently
create/kill tables in SQL Server, links management gets complicated.
Thanks for your suggestion, about my example, of selecting two fields as
unique identifier. I confess I didn't think of it. But the problem is
elsewhere : when you receive, from transactional systems, data in tables wit
h
no primary key (and this frequently happens), it would not be reasonable to
add a unique identifier when creating odbc link, as you may never be sure
about the existence of duplicates.
With ADPs, everything is more simple : you work with the database "as it
is", without interfering with risky adds. Roughly speaking, "what you see is
what you get". And of course the direct manipulation of SQL objects in
ACCESS, with no code writing, allows fast developments.
4. As a conclusion, I would say it is possible to find a solution, more or
less satisfying, to this RunSQL problem (In fact, the definite solution will
be to avoid this method). But the real fact is that there is galaxy between
ADPs and ODBC/ADO (in ACCESS world of course) ...
What is rather strange is that Microsoft has, for years, presented ADPs as
THE solution for client/server ACCESS apps.
Once again, thanks very much for your help and interest in these questions.
"Charles Wang[MSFT]" wrote:
> Hi,
> I am interested in this issue. Would you mind letting me know the result o
f
> the suggestions? If you need further assistance, feel free to let me know.
> I will be more than happy to be of assistance.
> Have a great day!
> Charles Wang
> Microsoft Online Community Support
>|||Hi Jason,
Appreciate your detailed response. I do understand your concerns. Just one
point that you mentioned I cannot understand clearly.
You said, "From now, ADPs don't work with SQL 2005 as far as building
purpose is concerned.". Did you mean that ADPs cannot work with SQL 2005
from now on? As far as I know, both Access 2003 and Access 2007 can work
well with SQL 2005 Express, Standard and Enterprise edtions.
Did you encounter some issue when you use ADP to work with SQL 2005? If so,
please post the issue here and I can assist you on it.
I performed a test with ADP and managed to update a SQL Server 2005 Express
table with primary key. Also, I managed to execute DoCmd.RunSQL on a no
primary key table in ADP:
I created a table in SQL 2005 Express:
CREATE TABLE [dbo].[Employee](
[First_Name] [varchar](50) COLLATE SQL_Latin1_General_CP1_CI_AS NOT
NULL,
[Last_Name] [varchar](50) COLLATE SQL_Latin1_General_CP1_CI_AS NOT N
ULL,
[Description] [varchar](50) COLLATE SQL_Latin1_General_CP1_CI_AS NUL
L
)
INSERT INTO Employee VALUES('F1','L1','F1 L1')
INSERT INTO Employee VALUES('F2','L2','F2 L2')
INSERT INTO Employee VALUES('F1','L1','F1 L1')
Then in ADP, I managed to run the query:
DoCmd.RunSQL "Update Employee SET Description='FX LX' WHERE First_Name =
'F1'"
For a table with no primary key, I think it is a by design limitation in
Access database (.mdb) and I have submited a feedback for this.
If you have any other questions or concerns, please feel free to let me
know. It is my pleasure to be of assistance.
Charles Wang
Microsoft Online Community Support
========================================
==============
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
========================================
==============
This posting is provided "AS IS" with no warranties, and confers no rights.
========================================
==============
Tuesday, March 20, 2012
Running Sql Server Developer Edition with VS 2005 and ASP.NET
I am having problems installing Sql Server Developer edition (2005) with VS 2005 and getting any ASP.NET projects to work.
It says SQl Server express must be installed.
I would like to use the full developer edition to link to my projects.
Can someone help?
Thanks,
Mike G
In your connection string in web.config in your ASP.Net projects, are you pointing to SQLExpress, or have you configured it to connect to your Dev Edition SQL Server? More details on your configuration and error message would help.|||I am having the same problem. When I try to add a new sql database to an asp.net web application using the following steps:
1. Right-click the App_Data folder
2. Select "Add New Item"
3. Select Sql Database
4. Change SQL Database name to xxxxxx.mdf
5. Click "Add"
I then get the following message:
"Connections to SQL Server Files (*.mdf) require SQL Server Express 2005 to function properly. Please verify the installation of the component or download from the URl: http:go.microsoft.com/fwlink/?linkID=49251."
I am using VS 2005 Professional and SQL Server 2005 Standard Edition. I want to be able to do this with SSE. In VS2005 I have gone to Tools...Options...Database Tools...Data Connections and changed the SQL Server Instance Name from SQLEXPRESS to MSSQLSERVER. Should I make it the name of my server?
Any help would be greatly appreciated.
John
|||By using App_Data it appears you're forced into using SQL Express, because you're defining a connection to a physical database file, rather than establishing a connection string to an existing server.
In my web.config file I configure an application variable called ConnectionString containing something like this:
Integrated Security=True;Data Source=MyServer;Initial Catalog=MyDatabase;Application Name=MyApp;
Then I configure a SQL Connection object and set the .ConnectionString property to the application connection string. After that all is well.
|||So does that mean the App_Data folder is only used with SQL Server Express and not to be used with SQL Server 2005?
John
Running Sql Server Developer Edition with VS 2005 and ASP.NET
I am having problems installing Sql Server Developer edition (2005) with VS 2005 and getting any ASP.NET projects to work.
It says SQl Server express must be installed.
I would like to use the full developer edition to link to my projects.
Can someone help?
Thanks,
Mike G
In your connection string in web.config in your ASP.Net projects, are you pointing to SQLExpress, or have you configured it to connect to your Dev Edition SQL Server? More details on your configuration and error message would help.|||I am having the same problem. When I try to add a new sql database to an asp.net web application using the following steps:
1. Right-click the App_Data folder
2. Select "Add New Item"
3. Select Sql Database
4. Change SQL Database name to xxxxxx.mdf
5. Click "Add"
I then get the following message:
"Connections to SQL Server Files (*.mdf) require SQL Server Express 2005 to function properly. Please verify the installation of the component or download from the URl: http:go.microsoft.com/fwlink/?linkID=49251."
I am using VS 2005 Professional and SQL Server 2005 Standard Edition. I want to be able to do this with SSE. In VS2005 I have gone to Tools...Options...Database Tools...Data Connections and changed the SQL Server Instance Name from SQLEXPRESS to MSSQLSERVER. Should I make it the name of my server?
Any help would be greatly appreciated.
John
|||By using App_Data it appears you're forced into using SQL Express, because you're defining a connection to a physical database file, rather than establishing a connection string to an existing server.
In my web.config file I configure an application variable called ConnectionString containing something like this:
Integrated Security=True;Data Source=MyServer;Initial Catalog=MyDatabase;Application Name=MyApp;
Then I configure a SQL Connection object and set the .ConnectionString property to the application connection string. After that all is well.
|||So does that mean the App_Data folder is only used with SQL Server Express and not to be used with SQL Server 2005?
John
Running SQL Server 2005 Dev Ed. and Express Ed. side by side.
I recieved the same error running both the SQL Svr Express SP1 and the SQL Svr SP1 updates. I resolved the problem with SQL Svr Express by installing the SQL Svr Express with Advanced Serives pakage. The SQL Svr SP1 still errors out with this message: Unexpected error ocurred: The following unexpected error ocurred <blank message> with an ok button. The following is the contents of the installtion log file:
7/14/2006 13:39:18.489 ================================================================================
07/14/2006 13:39:18.620 Hotfix package launched
07/14/2006 13:39:18.700 Successfully opened registry key: SOFTWARE\Microsoft\Windows\CurrentVersion
07/14/2006 13:39:18.800 Successfully read registry key: CommonFilesDir, string value = C:\Program Files\Common Files
07/14/2006 13:39:18.940 Successfully opened registry key: SOFTWARE\Microsoft\Windows\CurrentVersion
07/14/2006 13:39:19.060 Successfully read registry key: ProgramFilesDir, string value = C:\Program Files
07/14/2006 13:39:22.375 Successfully opened registry key: SOFTWARE\Microsoft\Windows\CurrentVersion
07/14/2006 13:39:22.535 Successfully read registry key: CommonFilesDir, string value = C:\Program Files\Common Files
07/14/2006 13:39:22.635 Successfully opened registry key: SOFTWARE\Microsoft\Windows\CurrentVersion
07/14/2006 13:39:22.756 Successfully read registry key: ProgramFilesDir, string value = C:\Program Files
07/14/2006 13:39:22.836 Local Computer:
07/14/2006 13:39:22.936 Target Details: SONYAS-LAP
07/14/2006 13:39:23.016 commonfilesdir = C:\Program Files\Common Files
07/14/2006 13:39:23.116 lcidsupportdir = e:\8960d915665e75cf26ff\1033
07/14/2006 13:39:23.256 programfilesdir = C:\Program Files
07/14/2006 13:39:23.356 supportdir = \\SONYAS-LAP\e$\8960d915665e75cf26ff
07/14/2006 13:39:23.477 supportdirlocal = e:\8960d915665e75cf26ff
07/14/2006 13:39:23.577 windir = C:\WINDOWS
07/14/2006 13:39:23.627 winsysdir = C:\WINDOWS\system32
07/14/2006 13:39:23.677
07/14/2006 13:39:23.707 Enumerating applicable products for this patch
07/14/2006 13:39:37.377 The patch installation could not proceed due to unexpected errors
07/14/2006 13:39:37.547
07/14/2006 13:39:37.708 Product Status Summary:
07/14/2006 13:39:38.629 Hotfix package closed
Doesn't really give much detail.
Moving to Setup so they can troubleshoot the issue w/ SQL SP1 patch.
Mike
Running SQL Server 2005 Dev Ed. and Express Ed. side by side.
Hi all,
Is it possible to run SQL Server 2005 Dev Ed. and the Express edition side by side on my development platform?
Thanks,
Andy
Yep works just fine, I do this on several machines|||Have you been able to apply SP1 to SQL Svr 2005 Dev Ed. & SQl Svr Express Ed.? I have both installed in my development environment, its been working just fine so far. But, when I try to run SP1 for either Ed. the install fails.
Any ideas?
Sunni
|||Be aware that the SP1 patch for Dev edition and the SP1 upgrade for Express Edition are two different things. There is not single download that will update both those editions.
You can download the Express Update from the Express download page. The patch for all non-Express Edtions, including Dev, can be found here.
The Express SP1 upgrade can both patch and install new instances, so be sure you're selecting your currently installed Instance Name when applying it to upgrade the existing instances.
I've not heard of specific issue for either of the SP1 updates, could you provide more information about the specific problems you're having? Any error messages? What does the log say?
Regards,
Mike Wachal
SQL Express team
-
Check out my tips for getting your answer faster and how to ask a good question: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=307712&SiteID=1
Running sql scripts
How does one run an sql script against a database then using sql management express.
I have the script and i connect to the correct database using the sql management express and execute the script. It even says that it completed successfully. But when i check the database there is nothing new added.
Is it somthing to do with the community preview version of sql management express??
thanks for any help
In Management Studio, the query window (where you run your query) can connect to different SQL instance/database from the Object Explorer (connect to a SQL instance when you open Management Studio). So check the dropdown list on the left of Execute(!) button to make sure your current query is connecting to the right database then execute the script. Before you check changes in the database, right click on the database ->select Refresh, then check the changes.Tuesday, February 21, 2012
Running SQL JOB for SQL Express >>>>>
The solution for running schedule tasks in SQL Express is to use a Task in the Windows Task Scheduler to call SQLCmd and run the script you want to run. You can set schedules, etc. using Windows Tasks.
SQL Express does not include the SQL Agent, which is the tool higher level Editions of SQL use to schedule jobs.
Regards,
Mike Wachal
SQL Express team
-
Please mark your thread as Answered when you get your solution.
Hi Mike,
Thanks for the information. I will try that. I also did a search and there is a program created by a company called Vale Software. They have a program named Express Agent that looks like it may work too. Thanks !!!
I do not understand why Microsoft went through the trouble of removing the Sql Agent scheduler from SQL 2005 Express. This is wrong for any product path/roadmap. There are many small applications, both in-house IT as well as distributed, that depend on the reliable SQL Server Agent Job scheduler.
I stopped using the Windows Task Scheduler years ago because you cannot count on it. It is not reliable. While it has improved since the NT4 and early Win2000 days, it is only marginally better due to a UI instead of the AT command line.
We need the service, SQLSERVERAGENT, to be included with SQL 2005 Express in order to migrate applications to 2005.
If you have a system that is configured for Client - Server - Notebook/offline and you utilize SQL2005 on the servers, you need SQL2005 Express on the Client and notebooks for replication. For the same reasons we distribute MSDE now, we would distribute SQL2005 Express in the future for the Notebook/offline engine. Out installations, updates, and backups, depend on the server and notebook being the same, (i.e. the same service names, the same scheduler, etc.). If the notbooks cannot have Express with the SQLSERVERAGENT service, then that complicates everything and increases the cost to everyone involved.
|||Yes, I definitely agree. I'm working on a product that uses a database, and that uses a free database for small business customers. We used to rely on MSDE. Now, we may rely on other non-MS databases, knowing that OLE DB allows us to access any database we need.
I don't think this is such a good commercial decision from MS.
Moreover, you can find in SQL Express all tools (stored procedures, tables) in msdb for creating and setting up jobs. The only thing you can't do regarding jobs is...starting them!!! This either does not give a good image of MS...
Running SQL JOB for SQL Express >>>>>
The solution for running schedule tasks in SQL Express is to use a Task in the Windows Task Scheduler to call SQLCmd and run the script you want to run. You can set schedules, etc. using Windows Tasks.
SQL Express does not include the SQL Agent, which is the tool higher level Editions of SQL use to schedule jobs.
Regards,
Mike Wachal
SQL Express team
-
Please mark your thread as Answered when you get your solution.
Hi Mike,
Thanks for the information. I will try that. I also did a search and there is a program created by a company called Vale Software. They have a program named Express Agent that looks like it may work too. Thanks !!!
I do not understand why Microsoft went through the trouble of removing the Sql Agent scheduler from SQL 2005 Express. This is wrong for any product path/roadmap. There are many small applications, both in-house IT as well as distributed, that depend on the reliable SQL Server Agent Job scheduler.
I stopped using the Windows Task Scheduler years ago because you cannot count on it. It is not reliable. While it has improved since the NT4 and early Win2000 days, it is only marginally better due to a UI instead of the AT command line.
We need the service, SQLSERVERAGENT, to be included with SQL 2005 Express in order to migrate applications to 2005.
If you have a system that is configured for Client - Server - Notebook/offline and you utilize SQL2005 on the servers, you need SQL2005 Express on the Client and notebooks for replication. For the same reasons we distribute MSDE now, we would distribute SQL2005 Express in the future for the Notebook/offline engine. Out installations, updates, and backups, depend on the server and notebook being the same, (i.e. the same service names, the same scheduler, etc.). If the notbooks cannot have Express with the SQLSERVERAGENT service, then that complicates everything and increases the cost to everyone involved.
|||
Yes, I definitely agree. I'm working on a product that uses a database, and that uses a free database for small business customers. We used to rely on MSDE. Now, we may rely on other non-MS databases, knowing that OLE DB allows us to access any database we need.
I don't think this is such a good commercial decision from MS.
Moreover, you can find in SQL Express all tools (stored procedures, tables) in msdb for creating and setting up jobs. The only thing you can't do regarding jobs is...starting them!!! This either does not give a good image of MS...
Running SQL JOB for SQL Express >>>>>
The solution for running schedule tasks in SQL Express is to use a Task in the Windows Task Scheduler to call SQLCmd and run the script you want to run. You can set schedules, etc. using Windows Tasks.
SQL Express does not include the SQL Agent, which is the tool higher level Editions of SQL use to schedule jobs.
Regards,
Mike Wachal
SQL Express team
-
Please mark your thread as Answered when you get your solution.
Hi Mike,
Thanks for the information. I will try that. I also did a search and there is a program created by a company called Vale Software. They have a program named Express Agent that looks like it may work too. Thanks !!!
I do not understand why Microsoft went through the trouble of removing the Sql Agent scheduler from SQL 2005 Express. This is wrong for any product path/roadmap. There are many small applications, both in-house IT as well as distributed, that depend on the reliable SQL Server Agent Job scheduler.
I stopped using the Windows Task Scheduler years ago because you cannot count on it. It is not reliable. While it has improved since the NT4 and early Win2000 days, it is only marginally better due to a UI instead of the AT command line.
We need the service, SQLSERVERAGENT, to be included with SQL 2005 Express in order to migrate applications to 2005.
If you have a system that is configured for Client - Server - Notebook/offline and you utilize SQL2005 on the servers, you need SQL2005 Express on the Client and notebooks for replication. For the same reasons we distribute MSDE now, we would distribute SQL2005 Express in the future for the Notebook/offline engine. Out installations, updates, and backups, depend on the server and notebook being the same, (i.e. the same service names, the same scheduler, etc.). If the notbooks cannot have Express with the SQLSERVERAGENT service, then that complicates everything and increases the cost to everyone involved.
|||Yes, I definitely agree. I'm working on a product that uses a database, and that uses a free database for small business customers. We used to rely on MSDE. Now, we may rely on other non-MS databases, knowing that OLE DB allows us to access any database we need.
I don't think this is such a good commercial decision from MS.
Moreover, you can find in SQL Express all tools (stored procedures, tables) in msdb for creating and setting up jobs. The only thing you can't do regarding jobs is...starting them!!! This either does not give a good image of MS...
Running Snort with MSDE/Server Express 2005
Is it possible to install SNORT with MSDE or SQL Server 2005 Express
Edition?
I'm trying to install this on a standalone desktop PC, running Windows XP
Pro SP2 that has been stripped of any non-essential services. I have
installed MSDE 2000A from
http://www.microsoft.com/downloads/details.aspx?FamilyID=413744d1-a0bc-479f-bafa-e4b278eb9147&DisplayLang=en
and then installed the latest version of snort, and WinPcap3.1. However when
I try and configure snort, I get an error message about ntwdblib.dll not
being found or registered. I have read an FAQ that says:
"This is the Microsoft SQL Server(tm) client DLL. This library is used by
client applications attempting to establish direct connections to an
installation of SQL Server, as opposed to connecting via ODBC or ADO. It is
provided by Microsoft as part of their SQL Server product, and is installed
as part of the SQL Server client package on the SQL Server CD-ROM.".
So I installed SQL Server 2005 Express Edition, in the hope that it would
install & register this file, but again, I'm receiving the same error.
Any help would be greatly appreciated.
BenHi
ntwdblib.dll is for db-library which no longer supported, but your msde
install would have created it. Did you check the DLL exists and is it on your
PATH? It should be in the system32 directory.
John
"benblackmore@.nospam.postalias" wrote:
> Hi,
> Is it possible to install SNORT with MSDE or SQL Server 2005 Express
> Edition?
> I'm trying to install this on a standalone desktop PC, running Windows XP
> Pro SP2 that has been stripped of any non-essential services. I have
> installed MSDE 2000A from
> http://www.microsoft.com/downloads/details.aspx?FamilyID=413744d1-a0bc-479f-bafa-e4b278eb9147&DisplayLang=en
> and then installed the latest version of snort, and WinPcap3.1. However when
> I try and configure snort, I get an error message about ntwdblib.dll not
> being found or registered. I have read an FAQ that says:
> "This is the Microsoft SQL Server(tm) client DLL. This library is used by
> client applications attempting to establish direct connections to an
> installation of SQL Server, as opposed to connecting via ODBC or ADO. It is
> provided by Microsoft as part of their SQL Server product, and is installed
> as part of the SQL Server client package on the SQL Server CD-ROM.".
> So I installed SQL Server 2005 Express Edition, in the hope that it would
> install & register this file, but again, I'm receiving the same error.
> Any help would be greatly appreciated.
> Ben
>
>|||Hi,
Thanks for the reply.
Yes, I even did a search of my entire C: drive for 'ntwdblib.dll', and it
found nothing.
Ben
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:0FE539E5-18EC-4D71-A4B7-13B014A34079@.microsoft.com...
> Hi
> ntwdblib.dll is for db-library which no longer supported, but your msde
> install would have created it. Did you check the DLL exists and is it on
> your
> PATH? It should be in the system32 directory.
> John
> "benblackmore@.nospam.postalias" wrote:
>> Hi,
>> Is it possible to install SNORT with MSDE or SQL Server 2005 Express
>> Edition?
>> I'm trying to install this on a standalone desktop PC, running Windows XP
>> Pro SP2 that has been stripped of any non-essential services. I have
>> installed MSDE 2000A from
>> http://www.microsoft.com/downloads/details.aspx?FamilyID=413744d1-a0bc-479f-bafa-e4b278eb9147&DisplayLang=en
>> and then installed the latest version of snort, and WinPcap3.1. However
>> when
>> I try and configure snort, I get an error message about ntwdblib.dll not
>> being found or registered. I have read an FAQ that says:
>> "This is the Microsoft SQL Server(tm) client DLL. This library is used by
>> client applications attempting to establish direct connections to an
>> installation of SQL Server, as opposed to connecting via ODBC or ADO. It
>> is
>> provided by Microsoft as part of their SQL Server product, and is
>> installed
>> as part of the SQL Server client package on the SQL Server CD-ROM.".
>> So I installed SQL Server 2005 Express Edition, in the hope that it would
>> install & register this file, but again, I'm receiving the same error.
>> Any help would be greatly appreciated.
>> Ben
>>|||Hi Ben
An installation of MSDE with "MDAC with additional client components" will
install DB-Library. You may want to enable logging for your installation by
using the /L*v option see
http://support.microsoft.com/default.aspx?scid=KB;EN-US;Q324998
John
"benblackmore@.nospam.postalias" wrote:
> Hi,
> Thanks for the reply.
> Yes, I even did a search of my entire C: drive for 'ntwdblib.dll', and it
> found nothing.
> Ben
>
> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> news:0FE539E5-18EC-4D71-A4B7-13B014A34079@.microsoft.com...
> > Hi
> >
> > ntwdblib.dll is for db-library which no longer supported, but your msde
> > install would have created it. Did you check the DLL exists and is it on
> > your
> > PATH? It should be in the system32 directory.
> >
> > John
> >
> > "benblackmore@.nospam.postalias" wrote:
> >
> >> Hi,
> >>
> >> Is it possible to install SNORT with MSDE or SQL Server 2005 Express
> >> Edition?
> >>
> >> I'm trying to install this on a standalone desktop PC, running Windows XP
> >> Pro SP2 that has been stripped of any non-essential services. I have
> >> installed MSDE 2000A from
> >> http://www.microsoft.com/downloads/details.aspx?FamilyID=413744d1-a0bc-479f-bafa-e4b278eb9147&DisplayLang=en
> >> and then installed the latest version of snort, and WinPcap3.1. However
> >> when
> >> I try and configure snort, I get an error message about ntwdblib.dll not
> >> being found or registered. I have read an FAQ that says:
> >>
> >> "This is the Microsoft SQL Server(tm) client DLL. This library is used by
> >> client applications attempting to establish direct connections to an
> >> installation of SQL Server, as opposed to connecting via ODBC or ADO. It
> >> is
> >> provided by Microsoft as part of their SQL Server product, and is
> >> installed
> >> as part of the SQL Server client package on the SQL Server CD-ROM.".
> >>
> >> So I installed SQL Server 2005 Express Edition, in the hope that it would
> >> install & register this file, but again, I'm receiving the same error.
> >>
> >> Any help would be greatly appreciated.
> >>
> >> Ben
> >>
> >>
> >>
>
>|||Hi Ben,
None of the SQL Server 2005 client tools have any dependency on
ntwdblib.dll and it is no longer shipped with SQL Server 2005.
Ntwdblib.dll is the DLL for the old DB-Library API. DB-Library is
deprecated with SQL Server 2005; SQL Server 2005 no longer includes the
DB-Library dll, and anyone wanting to run a DB-Library application against
SQL Server 2005 needs to get the dll from a previous version of SQL Server.
From the SQL Server 2005 Books Online:
http://msdn2.microsoft.com/en-us/library/ms143729(en-US,SQL.90).aspx
To run DB-Library or Embedded SQL applications you must have available the
DB-Library DLL from SQL Server version 6.5, SQL Server 7.0, or SQL Server
2000.
I think you have to copy the ntwdblib.dll from another computer which
contains and register it manually.
Best regards,
Vincent Xu
Microsoft Online Partner Support
======================================================Get Secure! - www.microsoft.com/security
======================================================When responding to posts, please "Reply to Group" via your newsreader so
that others
may learn and benefit from this issue.
======================================================This posting is provided "AS IS" with no warranties,and confers no rights.
======================================================>>Reply-To: <benblackmore@.nospam.postalias>
>>From: <benblackmore@.nospam.postalias>
>>Subject: Running Snort with MSDE/Server Express 2005
>>Date: Mon, 26 Jun 2006 11:58:47 +0100
>>Lines: 27
>>X-Priority: 3
>>X-MSMail-Priority: Normal
>>X-Newsreader: Microsoft Outlook Express 6.00.2900.2869
>>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2869
>>X-RFC2646: Format=Flowed; Original
>>Message-ID: <uX1hB#QmGHA.4268@.TK2MSFTNGP05.phx.gbl>
>>Newsgroups: microsoft.public.sqlserver.server
>>NNTP-Posting-Host: host217-37-28-250.in-addr.btopenworld.com 217.37.28.250
>>Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP05.phx.gbl
>>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.server:436220
>>X-Tomcat-NG: microsoft.public.sqlserver.server
>>Hi,
>>Is it possible to install SNORT with MSDE or SQL Server 2005 Express
>>Edition?
>>I'm trying to install this on a standalone desktop PC, running Windows XP
>>Pro SP2 that has been stripped of any non-essential services. I have
>>installed MSDE 2000A from
>>http://www.microsoft.com/downloads/details.aspx?FamilyID=413744d1-a0bc-479
f-bafa-e4b278eb9147&DisplayLang=en
>>and then installed the latest version of snort, and WinPcap3.1. However
when
>>I try and configure snort, I get an error message about ntwdblib.dll not
>>being found or registered. I have read an FAQ that says:
>>"This is the Microsoft SQL Server(tm) client DLL. This library is used by
>>client applications attempting to establish direct connections to an
>>installation of SQL Server, as opposed to connecting via ODBC or ADO. It
is
>>provided by Microsoft as part of their SQL Server product, and is
installed
>>as part of the SQL Server client package on the SQL Server CD-ROM.".
>>So I installed SQL Server 2005 Express Edition, in the hope that it would
>>install & register this file, but again, I'm receiving the same error.
>>Any help would be greatly appreciated.
>>Ben
>>|||Hi Vincent,
Thanks for the reply.
I think we have a spare SQL 2000 license from our MAPS subscription, if I
install it, and use this rather than the 2005 version, this should register
the ntwdblib.dll, and work? I don't think we need the latest version of SQL,
it's only for snort to log to, which is why I initially tried the MSDE, but
failing that, I assume it can do this using SQL 2000 as well.
Many thanks
Ben
"Vincent Xu [MSFT]" <v-xuwen@.online.microsoft.com> wrote in message
news:Gtf%23XxYmGHA.5184@.TK2MSFTNGXA01.phx.gbl...
> Hi Ben,
> None of the SQL Server 2005 client tools have any dependency on
> ntwdblib.dll and it is no longer shipped with SQL Server 2005.
> Ntwdblib.dll is the DLL for the old DB-Library API. DB-Library is
> deprecated with SQL Server 2005; SQL Server 2005 no longer includes the
> DB-Library dll, and anyone wanting to run a DB-Library application against
> SQL Server 2005 needs to get the dll from a previous version of SQL
> Server.
> From the SQL Server 2005 Books Online:
> http://msdn2.microsoft.com/en-us/library/ms143729(en-US,SQL.90).aspx
> To run DB-Library or Embedded SQL applications you must have available the
> DB-Library DLL from SQL Server version 6.5, SQL Server 7.0, or SQL Server
> 2000.
> I think you have to copy the ntwdblib.dll from another computer which
> contains and register it manually.
>
> Best regards,
> Vincent Xu
> Microsoft Online Partner Support
> ======================================================> Get Secure! - www.microsoft.com/security
> ======================================================> When responding to posts, please "Reply to Group" via your newsreader so
> that others
> may learn and benefit from this issue.
> ======================================================> This posting is provided "AS IS" with no warranties,and confers no rights.
> ======================================================>
> --
>>Reply-To: <benblackmore@.nospam.postalias>
>>From: <benblackmore@.nospam.postalias>
>>Subject: Running Snort with MSDE/Server Express 2005
>>Date: Mon, 26 Jun 2006 11:58:47 +0100
>>Lines: 27
>>X-Priority: 3
>>X-MSMail-Priority: Normal
>>X-Newsreader: Microsoft Outlook Express 6.00.2900.2869
>>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2869
>>X-RFC2646: Format=Flowed; Original
>>Message-ID: <uX1hB#QmGHA.4268@.TK2MSFTNGP05.phx.gbl>
>>Newsgroups: microsoft.public.sqlserver.server
>>NNTP-Posting-Host: host217-37-28-250.in-addr.btopenworld.com
>>217.37.28.250
>>Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP05.phx.gbl
>>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.server:436220
>>X-Tomcat-NG: microsoft.public.sqlserver.server
>>Hi,
>>Is it possible to install SNORT with MSDE or SQL Server 2005 Express
>>Edition?
>>I'm trying to install this on a standalone desktop PC, running Windows XP
>>Pro SP2 that has been stripped of any non-essential services. I have
>>installed MSDE 2000A from
>>http://www.microsoft.com/downloads/details.aspx?FamilyID=413744d1-a0bc-479
> f-bafa-e4b278eb9147&DisplayLang=en
>>and then installed the latest version of snort, and WinPcap3.1. However
> when
>>I try and configure snort, I get an error message about ntwdblib.dll not
>>being found or registered. I have read an FAQ that says:
>>"This is the Microsoft SQL Server(tm) client DLL. This library is used by
>>client applications attempting to establish direct connections to an
>>installation of SQL Server, as opposed to connecting via ODBC or ADO. It
> is
>>provided by Microsoft as part of their SQL Server product, and is
> installed
>>as part of the SQL Server client package on the SQL Server CD-ROM.".
>>So I installed SQL Server 2005 Express Edition, in the hope that it would
>>install & register this file, but again, I'm receiving the same error.
>>Any help would be greatly appreciated.
>>Ben
>>
>|||Hi Ben
That should be fine if you have the licences. MSDE should have been fine but
I don't have enough information to say why it did not install this library.
John
"benblackmore@.nospam.postalias" wrote:
> Hi Vincent,
> Thanks for the reply.
> I think we have a spare SQL 2000 license from our MAPS subscription, if I
> install it, and use this rather than the 2005 version, this should register
> the ntwdblib.dll, and work? I don't think we need the latest version of SQL,
> it's only for snort to log to, which is why I initially tried the MSDE, but
> failing that, I assume it can do this using SQL 2000 as well.
> Many thanks
> Ben
> "Vincent Xu [MSFT]" <v-xuwen@.online.microsoft.com> wrote in message
> news:Gtf%23XxYmGHA.5184@.TK2MSFTNGXA01.phx.gbl...
> > Hi Ben,
> >
> > None of the SQL Server 2005 client tools have any dependency on
> > ntwdblib.dll and it is no longer shipped with SQL Server 2005.
> >
> > Ntwdblib.dll is the DLL for the old DB-Library API. DB-Library is
> > deprecated with SQL Server 2005; SQL Server 2005 no longer includes the
> > DB-Library dll, and anyone wanting to run a DB-Library application against
> > SQL Server 2005 needs to get the dll from a previous version of SQL
> > Server.
> > From the SQL Server 2005 Books Online:
> >
> > http://msdn2.microsoft.com/en-us/library/ms143729(en-US,SQL.90).aspx
> >
> > To run DB-Library or Embedded SQL applications you must have available the
> > DB-Library DLL from SQL Server version 6.5, SQL Server 7.0, or SQL Server
> > 2000.
> >
> > I think you have to copy the ntwdblib.dll from another computer which
> > contains and register it manually.
> >
> >
> > Best regards,
> >
> > Vincent Xu
> > Microsoft Online Partner Support
> >
> > ======================================================> > Get Secure! - www.microsoft.com/security
> > ======================================================> > When responding to posts, please "Reply to Group" via your newsreader so
> > that others
> > may learn and benefit from this issue.
> > ======================================================> > This posting is provided "AS IS" with no warranties,and confers no rights.
> > ======================================================> >
> >
> >
> > --
> >>Reply-To: <benblackmore@.nospam.postalias>
> >>From: <benblackmore@.nospam.postalias>
> >>Subject: Running Snort with MSDE/Server Express 2005
> >>Date: Mon, 26 Jun 2006 11:58:47 +0100
> >>Lines: 27
> >>X-Priority: 3
> >>X-MSMail-Priority: Normal
> >>X-Newsreader: Microsoft Outlook Express 6.00.2900.2869
> >>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2869
> >>X-RFC2646: Format=Flowed; Original
> >>Message-ID: <uX1hB#QmGHA.4268@.TK2MSFTNGP05.phx.gbl>
> >>Newsgroups: microsoft.public.sqlserver.server
> >>NNTP-Posting-Host: host217-37-28-250.in-addr.btopenworld.com
> >>217.37.28.250
> >>Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP05.phx.gbl
> >>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.server:436220
> >>X-Tomcat-NG: microsoft.public.sqlserver.server
> >>
> >>Hi,
> >>
> >>Is it possible to install SNORT with MSDE or SQL Server 2005 Express
> >>Edition?
> >>
> >>I'm trying to install this on a standalone desktop PC, running Windows XP
> >>Pro SP2 that has been stripped of any non-essential services. I have
> >>installed MSDE 2000A from
> >>http://www.microsoft.com/downloads/details.aspx?FamilyID=413744d1-a0bc-479
> > f-bafa-e4b278eb9147&DisplayLang=en
> >>and then installed the latest version of snort, and WinPcap3.1. However
> > when
> >>I try and configure snort, I get an error message about ntwdblib.dll not
> >>being found or registered. I have read an FAQ that says:
> >>
> >>"This is the Microsoft SQL Server(tm) client DLL. This library is used by
> >>client applications attempting to establish direct connections to an
> >>installation of SQL Server, as opposed to connecting via ODBC or ADO. It
> > is
> >>provided by Microsoft as part of their SQL Server product, and is
> > installed
> >>as part of the SQL Server client package on the SQL Server CD-ROM.".
> >>
> >>So I installed SQL Server 2005 Express Edition, in the hope that it would
> >>install & register this file, but again, I'm receiving the same error.
> >>
> >>Any help would be greatly appreciated.
> >>
> >>Ben
> >>
> >>
> >>
> >
>
>|||Hi,
Glad to provide information. :)
Have a good day!
Best regards,
Vincent Xu
Microsoft Online Partner Support
======================================================Get Secure! - www.microsoft.com/security
======================================================When responding to posts, please "Reply to Group" via your newsreader so
that others
may learn and benefit from this issue.
======================================================This posting is provided "AS IS" with no warranties,and confers no rights.
======================================================>>Thread-Topic: Running Snort with MSDE/Server Express 2005
>>thread-index: AcaZ0SfQrlf7tnksTPWQc01FIfFYRQ==>>X-WBNR-Posting-Host: 62.6.139.10
>>From: =?Utf-8?B?Sm9obiBCZWxs?= <jbellnewsposts@.hotmail.com>
>>References: <uX1hB#QmGHA.4268@.TK2MSFTNGP05.phx.gbl>
<Gtf#XxYmGHA.5184@.TK2MSFTNGXA01.phx.gbl>
<u3ZK6dcmGHA.4952@.TK2MSFTNGP04.phx.gbl>
>>Subject: Re: Running Snort with MSDE/Server Express 2005
>>Date: Tue, 27 Jun 2006 03:05:02 -0700
>>Lines: 119
>>Message-ID: <42964C12-AE6E-4BA9-A759-8B190A508CAF@.microsoft.com>
>>MIME-Version: 1.0
>>Content-Type: text/plain;
>> charset="Utf-8"
>>Content-Transfer-Encoding: 7bit
>>X-Newsreader: Microsoft CDO for Windows 2000
>>Content-Class: urn:content-classes:message
>>Importance: normal
>>Priority: normal
>>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
>>Newsgroups: microsoft.public.sqlserver.server
>>Path: TK2MSFTNGXA01.phx.gbl
>>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.server:436381
>>NNTP-Posting-Host: TK2MSFTNGXA01.phx.gbl 10.40.2.250
>>X-Tomcat-NG: microsoft.public.sqlserver.server
>>Hi Ben
>>That should be fine if you have the licences. MSDE should have been fine
but
>>I don't have enough information to say why it did not install this
library.
>>John
>>"benblackmore@.nospam.postalias" wrote:
>> Hi Vincent,
>> Thanks for the reply.
>> I think we have a spare SQL 2000 license from our MAPS subscription, if
I
>> install it, and use this rather than the 2005 version, this should
register
>> the ntwdblib.dll, and work? I don't think we need the latest version of
SQL,
>> it's only for snort to log to, which is why I initially tried the MSDE,
but
>> failing that, I assume it can do this using SQL 2000 as well.
>> Many thanks
>> Ben
>> "Vincent Xu [MSFT]" <v-xuwen@.online.microsoft.com> wrote in message
>> news:Gtf%23XxYmGHA.5184@.TK2MSFTNGXA01.phx.gbl...
>> > Hi Ben,
>> >
>> > None of the SQL Server 2005 client tools have any dependency on
>> > ntwdblib.dll and it is no longer shipped with SQL Server 2005.
>> >
>> > Ntwdblib.dll is the DLL for the old DB-Library API. DB-Library is
>> > deprecated with SQL Server 2005; SQL Server 2005 no longer includes
the
>> > DB-Library dll, and anyone wanting to run a DB-Library application
against
>> > SQL Server 2005 needs to get the dll from a previous version of SQL
>> > Server.
>> > From the SQL Server 2005 Books Online:
>> >
>> > http://msdn2.microsoft.com/en-us/library/ms143729(en-US,SQL.90).aspx
>> >
>> > To run DB-Library or Embedded SQL applications you must have
available the
>> > DB-Library DLL from SQL Server version 6.5, SQL Server 7.0, or SQL
Server
>> > 2000.
>> >
>> > I think you have to copy the ntwdblib.dll from another computer which
>> > contains and register it manually.
>> >
>> >
>> > Best regards,
>> >
>> > Vincent Xu
>> > Microsoft Online Partner Support
>> >
>> > ======================================================>> > Get Secure! - www.microsoft.com/security
>> > ======================================================>> > When responding to posts, please "Reply to Group" via your newsreader
so
>> > that others
>> > may learn and benefit from this issue.
>> > ======================================================>> > This posting is provided "AS IS" with no warranties,and confers no
rights.
>> > ======================================================>> >
>> >
>> >
>> > --
>> >>Reply-To: <benblackmore@.nospam.postalias>
>> >>From: <benblackmore@.nospam.postalias>
>> >>Subject: Running Snort with MSDE/Server Express 2005
>> >>Date: Mon, 26 Jun 2006 11:58:47 +0100
>> >>Lines: 27
>> >>X-Priority: 3
>> >>X-MSMail-Priority: Normal
>> >>X-Newsreader: Microsoft Outlook Express 6.00.2900.2869
>> >>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2869
>> >>X-RFC2646: Format=Flowed; Original
>> >>Message-ID: <uX1hB#QmGHA.4268@.TK2MSFTNGP05.phx.gbl>
>> >>Newsgroups: microsoft.public.sqlserver.server
>> >>NNTP-Posting-Host: host217-37-28-250.in-addr.btopenworld.com
>> >>217.37.28.250
>> >>Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP05.phx.gbl
>> >>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.server:436220
>> >>X-Tomcat-NG: microsoft.public.sqlserver.server
>> >>
>> >>Hi,
>> >>
>> >>Is it possible to install SNORT with MSDE or SQL Server 2005 Express
>> >>Edition?
>> >>
>> >>I'm trying to install this on a standalone desktop PC, running
Windows XP
>> >>Pro SP2 that has been stripped of any non-essential services. I have
>> >>installed MSDE 2000A from
>>http://www.microsoft.com/downloads/details.aspx?FamilyID=413744d1-a0bc-47
9
>> > f-bafa-e4b278eb9147&DisplayLang=en
>> >>and then installed the latest version of snort, and WinPcap3.1.
However
>> > when
>> >>I try and configure snort, I get an error message about ntwdblib.dll
not
>> >>being found or registered. I have read an FAQ that says:
>> >>
>> >>"This is the Microsoft SQL Server(tm) client DLL. This library is
used by
>> >>client applications attempting to establish direct connections to an
>> >>installation of SQL Server, as opposed to connecting via ODBC or
ADO. It
>> > is
>> >>provided by Microsoft as part of their SQL Server product, and is
>> > installed
>> >>as part of the SQL Server client package on the SQL Server CD-ROM.".
>> >>
>> >>So I installed SQL Server 2005 Express Edition, in the hope that it
would
>> >>install & register this file, but again, I'm receiving the same
error.
>> >>
>> >>Any help would be greatly appreciated.
>> >>
>> >>Ben
>> >>
>> >>
>> >>
>> >
>>
>>
Running Snort with MSDE/Server Express 2005
Is it possible to install SNORT with MSDE or SQL Server 2005 Express
Edition?
I'm trying to install this on a standalone desktop PC, running Windows XP
Pro SP2 that has been stripped of any non-essential services. I have
installed MSDE 2000A from
http://www.microsoft.com/downloads/...&DisplayLang=en
and then installed the latest version of snort, and WinPcap3.1. However when
I try and configure snort, I get an error message about ntwdblib.dll not
being found or registered. I have read an FAQ that says:
"This is the Microsoft SQL Server(tm) client DLL. This library is used by
client applications attempting to establish direct connections to an
installation of SQL Server, as opposed to connecting via ODBC or ADO. It is
provided by Microsoft as part of their SQL Server product, and is installed
as part of the SQL Server client package on the SQL Server CD-ROM.".
So I installed SQL Server 2005 Express Edition, in the hope that it would
install & register this file, but again, I'm receiving the same error.
Any help would be greatly appreciated.
BenHi
ntwdblib.dll is for db-library which no longer supported, but your msde
install would have created it. Did you check the DLL exists and is it on you
r
PATH? It should be in the system32 directory.
John
"benblackmore@.nospam.postalias" wrote:
> Hi,
> Is it possible to install SNORT with MSDE or SQL Server 2005 Express
> Edition?
> I'm trying to install this on a standalone desktop PC, running Windows XP
> Pro SP2 that has been stripped of any non-essential services. I have
> installed MSDE 2000A from
> http://www.microsoft.com/downloads/...&DisplayLang=en
> and then installed the latest version of snort, and WinPcap3.1. However wh
en
> I try and configure snort, I get an error message about ntwdblib.dll not
> being found or registered. I have read an FAQ that says:
> "This is the Microsoft SQL Server(tm) client DLL. This library is used by
> client applications attempting to establish direct connections to an
> installation of SQL Server, as opposed to connecting via ODBC or ADO. It i
s
> provided by Microsoft as part of their SQL Server product, and is installe
d
> as part of the SQL Server client package on the SQL Server CD-ROM.".
> So I installed SQL Server 2005 Express Edition, in the hope that it would
> install & register this file, but again, I'm receiving the same error.
> Any help would be greatly appreciated.
> Ben
>
>|||Hi,
Thanks for the reply.
Yes, I even did a search of my entire C: drive for 'ntwdblib.dll', and it
found nothing.
Ben
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:0FE539E5-18EC-4D71-A4B7-13B014A34079@.microsoft.com...[vbcol=seagreen]
> Hi
> ntwdblib.dll is for db-library which no longer supported, but your msde
> install would have created it. Did you check the DLL exists and is it on
> your
> PATH? It should be in the system32 directory.
> John
> "benblackmore@.nospam.postalias" wrote:
>|||Hi Ben
An installation of MSDE with "MDAC with additional client components" will
install DB-Library. You may want to enable logging for your installation by
using the /L*v option see
http://support.microsoft.com/defaul...B;EN-US;Q324998
John
"benblackmore@.nospam.postalias" wrote:
> Hi,
> Thanks for the reply.
> Yes, I even did a search of my entire C: drive for 'ntwdblib.dll', and it
> found nothing.
> Ben
>
> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> news:0FE539E5-18EC-4D71-A4B7-13B014A34079@.microsoft.com...
>
>|||Hi
ntwdblib.dll is for db-library which no longer supported, but your msde
install would have created it. Did you check the DLL exists and is it on you
r
PATH? It should be in the system32 directory.
John
"benblackmore@.nospam.postalias" wrote:
> Hi,
> Is it possible to install SNORT with MSDE or SQL Server 2005 Express
> Edition?
> I'm trying to install this on a standalone desktop PC, running Windows XP
> Pro SP2 that has been stripped of any non-essential services. I have
> installed MSDE 2000A from
> http://www.microsoft.com/downloads/...&DisplayLang=en
> and then installed the latest version of snort, and WinPcap3.1. However wh
en
> I try and configure snort, I get an error message about ntwdblib.dll not
> being found or registered. I have read an FAQ that says:
> "This is the Microsoft SQL Server(tm) client DLL. This library is used by
> client applications attempting to establish direct connections to an
> installation of SQL Server, as opposed to connecting via ODBC or ADO. It i
s
> provided by Microsoft as part of their SQL Server product, and is installe
d
> as part of the SQL Server client package on the SQL Server CD-ROM.".
> So I installed SQL Server 2005 Express Edition, in the hope that it would
> install & register this file, but again, I'm receiving the same error.
> Any help would be greatly appreciated.
> Ben
>
>|||Hi,
Thanks for the reply.
Yes, I even did a search of my entire C: drive for 'ntwdblib.dll', and it
found nothing.
Ben
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:0FE539E5-18EC-4D71-A4B7-13B014A34079@.microsoft.com...[vbcol=seagreen]
> Hi
> ntwdblib.dll is for db-library which no longer supported, but your msde
> install would have created it. Did you check the DLL exists and is it on
> your
> PATH? It should be in the system32 directory.
> John
> "benblackmore@.nospam.postalias" wrote:
>|||Hi Ben
An installation of MSDE with "MDAC with additional client components" will
install DB-Library. You may want to enable logging for your installation by
using the /L*v option see
http://support.microsoft.com/defaul...B;EN-US;Q324998
John
"benblackmore@.nospam.postalias" wrote:
> Hi,
> Thanks for the reply.
> Yes, I even did a search of my entire C: drive for 'ntwdblib.dll', and it
> found nothing.
> Ben
>
> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> news:0FE539E5-18EC-4D71-A4B7-13B014A34079@.microsoft.com...
>
>|||Hi Ben,
None of the SQL Server 2005 client tools have any dependency on
ntwdblib.dll and it is no longer shipped with SQL Server 2005.
Ntwdblib.dll is the DLL for the old DB-Library API. DB-Library is
deprecated with SQL Server 2005; SQL Server 2005 no longer includes the
DB-Library dll, and anyone wanting to run a DB-Library application against
SQL Server 2005 needs to get the dll from a previous version of SQL Server.
From the SQL Server 2005 Books Online:
http://msdn2.microsoft.com/en-us/library/ms143729(en-US,SQL.90).aspx
To run DB-Library or Embedded SQL applications you must have available the
DB-Library DLL from SQL Server version 6.5, SQL Server 7.0, or SQL Server
2000.
I think you have to copy the ntwdblib.dll from another computer which
contains and register it manually.
Best regards,
Vincent Xu
Microsoft Online Partner Support
========================================
==============
Get Secure! - www.microsoft.com/security
========================================
==============
When responding to posts, please "Reply to Group" via your newsreader so
that others
may learn and benefit from this issue.
========================================
==============
This posting is provided "AS IS" with no warranties,and confers no rights.
========================================
==============
--[vbcol=seagreen]
f-bafa-e4b278eb9147&DisplayLang=en[vbcol=seagreen]
when[vbcol=seagreen]
is[vbcol=seagreen]
installed[vbcol=seagreen]|||Hi Ben,
None of the SQL Server 2005 client tools have any dependency on
ntwdblib.dll and it is no longer shipped with SQL Server 2005.
Ntwdblib.dll is the DLL for the old DB-Library API. DB-Library is
deprecated with SQL Server 2005; SQL Server 2005 no longer includes the
DB-Library dll, and anyone wanting to run a DB-Library application against
SQL Server 2005 needs to get the dll from a previous version of SQL Server.
From the SQL Server 2005 Books Online:
http://msdn2.microsoft.com/en-us/library/ms143729(en-US,SQL.90).aspx
To run DB-Library or Embedded SQL applications you must have available the
DB-Library DLL from SQL Server version 6.5, SQL Server 7.0, or SQL Server
2000.
I think you have to copy the ntwdblib.dll from another computer which
contains and register it manually.
Best regards,
Vincent Xu
Microsoft Online Partner Support
========================================
==============
Get Secure! - www.microsoft.com/security
========================================
==============
When responding to posts, please "Reply to Group" via your newsreader so
that others
may learn and benefit from this issue.
========================================
==============
This posting is provided "AS IS" with no warranties,and confers no rights.
========================================
==============
--[vbcol=seagreen]
f-bafa-e4b278eb9147&DisplayLang=en[vbcol=seagreen]
when[vbcol=seagreen]
is[vbcol=seagreen]
installed[vbcol=seagreen]|||Hi Vincent,
Thanks for the reply.
I think we have a spare SQL 2000 license from our MAPS subscription, if I
install it, and use this rather than the 2005 version, this should register
the ntwdblib.dll, and work? I don't think we need the latest version of SQL,
it's only for snort to log to, which is why I initially tried the MSDE, but
failing that, I assume it can do this using SQL 2000 as well.
Many thanks
Ben
"Vincent Xu [MSFT]" <v-xuwen@.online.microsoft.com> wrote in message
news:Gtf%23XxYmGHA.5184@.TK2MSFTNGXA01.phx.gbl...
> Hi Ben,
> None of the SQL Server 2005 client tools have any dependency on
> ntwdblib.dll and it is no longer shipped with SQL Server 2005.
> Ntwdblib.dll is the DLL for the old DB-Library API. DB-Library is
> deprecated with SQL Server 2005; SQL Server 2005 no longer includes the
> DB-Library dll, and anyone wanting to run a DB-Library application against
> SQL Server 2005 needs to get the dll from a previous version of SQL
> Server.
> From the SQL Server 2005 Books Online:
> http://msdn2.microsoft.com/en-us/library/ms143729(en-US,SQL.90).aspx
> To run DB-Library or Embedded SQL applications you must have available the
> DB-Library DLL from SQL Server version 6.5, SQL Server 7.0, or SQL Server
> 2000.
> I think you have to copy the ntwdblib.dll from another computer which
> contains and register it manually.
>
> Best regards,
> Vincent Xu
> Microsoft Online Partner Support
> ========================================
==============
> Get Secure! - www.microsoft.com/security
> ========================================
==============
> When responding to posts, please "Reply to Group" via your newsreader so
> that others
> may learn and benefit from this issue.
> ========================================
==============
> This posting is provided "AS IS" with no warranties,and confers no rights.
> ========================================
==============
>
> --
> f-bafa-e4b278eb9147&DisplayLang=en
> when
> is
> installed
>