When i enter http://akor.alternatifim.com/
i get the error below
Microsoft OLE DB Provider for ODBC Drivers error '80040e37'
[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid object name 'tblSARKICIM'.
The SQL statement is so simple like
Select * from tblSARKICIM
However when i change the SQL statement Select * from lyric.tblSARKICIM
lyric is username and owner of the tables.
Problem is solved. I transfer the My SQL Server and then this problem occurs and i don't want change all my SQL statements.
What can i do?Going to need to see the code.|||Can I ask, why does anyone feel the need to create database objects under any owner other than dbo?
I've always seen it cause more trouble than it's worth.
And if you want tables with the same name, why not just create another database?|||I am running that SQL Server with hosting firm, and can not see user of dbo.
What can i do for that? If administrators give Database Creators privilage to user lyric, is the problem solved? Or i need to change the owner of the tables to dbo?
I don't think there is a wrong with the code, because it was running without problem before transfering db.
Thanks for your helps.|||then the only work around is to instruct your web application (as I can see) to connect to the database server with that user (lyric) credentials.
This is the way that SQLServer works: when you specify an incomplete object qulificator (eg. DBname.Owner.ObjectName), then SQL first tries with current db, and current user as a default. Then switch to dbo (in place of owner). If all tose failed, then an exception of "Invalid object name ..." is thrown.
So if all your objects have the lyric user as their owner, you have two options to query them:
First: select * from lyric.tbl1 (works for any authenticate user that has select permissions on that tbl1 table) or,
Second: select * from tbl1 (works only if the current user is lyric)|||then the only work around is to instruct your web application (as I can see) to connect to the database server with that user (lyric) credentials.
This is the way that SQLServer works: when you specify an incomplete object qulificator (eg. DBname.Owner.ObjectName), then SQL first tries with current db, and current user as a default. Then switch to dbo (in place of owner). If all tose failed, then an exception of "Invalid object name ..." is thrown.
So if all your objects have the lyric user as their owner, you have two options to query them:
First: select * from lyric.tbl1 (works for any authenticate user that has select permissions on that tbl1 table) or,
Second: select * from tbl1 (works only if the current user is lyric)
DB owner is lyric and if i perform the query with lyric.name_of_table it runs without any errors. However changing all query user_name.table_name will be very difficult for me.
For that reason, i want to use query like select blah blah from tbl1 not lyric.tbl1
Is there a way to determine and change the current user? Or i need to change the owner of the table. And What will be do if administrator give lyric to Database Creators privilage (Server Role)
Thanks for your help|||I use that command and change the owner of the db lyric to dbo
And it is working now, thanks for your help :)
EXEC sp_changeobjectowner 'lyric.tblSARKICIM', 'dbo'
Showing posts with label odbc. Show all posts
Showing posts with label odbc. Show all posts
Friday, March 23, 2012
Wednesday, March 21, 2012
Invalid identifier/column names after Upsize Access data to SQL Se
I have been asked to maintain an Access 2000 database which is a code front
end linked by ODBC to a SQL Server 2005 back end. (Originally the data was
in an Access database but was later moved to SQL Server 2005 by the Upsizing
tools.)
Some tables have column names which do not conform to the rules given in SQL
Books Online - there are field names with embedded spaces, first character
not a-z or A-Z, name contains '/' and two names which are T-SQL reserved
words. When the tables are viewed via Management Studio, these 'odd' names
are enclosed in square brackets.
The production system is working in this state, but when I try to set up a
test environment on a stand-alone PC, I cannot access these tables. If I try
to link them I get 'ODBC -- Call failed', and if I try to import them I get
error messages about various column names. I can only link to, or import
other tables which do not have these 'odd' field names. If I rename the
columns in SQL server then I can import or link them with no problem.
(My PC has the latest service packs for SQL Server 2005 and Office 2003, and
MDAC 2.8 SP1.)
Somehow the production system works with this data but my test PC doesn't.
What do I need to do on my test PC to use this data with the original 'odd'
column names?
How are you linking the tables? You can write DAO/VBA code to pass the
correctly-delimited table names.
Frankly, you'd be better off just changing the names to conform to
SQLS identifier rules. Having non-compliant names is just going to
cause more headaches down the road. Take the hit now before you've
deployed the app.
-mary
On Fri, 22 Jun 2007 07:54:04 -0700, didub
<didub@.discussions.microsoft.com> wrote:
>I have been asked to maintain an Access 2000 database which is a code front
>end linked by ODBC to a SQL Server 2005 back end. (Originally the data was
>in an Access database but was later moved to SQL Server 2005 by the Upsizing
>tools.)
>Some tables have column names which do not conform to the rules given in SQL
>Books Online - there are field names with embedded spaces, first character
>not a-z or A-Z, name contains '/' and two names which are T-SQL reserved
>words. When the tables are viewed via Management Studio, these 'odd' names
>are enclosed in square brackets.
>The production system is working in this state, but when I try to set up a
>test environment on a stand-alone PC, I cannot access these tables. If I try
>to link them I get 'ODBC -- Call failed', and if I try to import them I get
>error messages about various column names. I can only link to, or import
>other tables which do not have these 'odd' field names. If I rename the
>columns in SQL server then I can import or link them with no problem.
>(My PC has the latest service packs for SQL Server 2005 and Office 2003, and
>MDAC 2.8 SP1.)
>Somehow the production system works with this data but my test PC doesn't.
>What do I need to do on my test PC to use this data with the original 'odd'
>column names?
|||I agree that the column names should be changed to satisfy SQL naming rules,
and I plan to do that, but that is not my first priority.
This app. was created and deployed several years ago by someone who is no
longer with the company. On the live server and desktops it is working with
these invalid names.
My first objective was to install a copy of the system on my own PC so I can
take it apart and plan some major changes and bug fixes. So ideally I would
just like to get my test system working as the live system does.
My guess is that there are some ODBC related settings that I need to change.
Or perhaps there is something I need to do on the SQL Server database. I
have searched Knowledgebase and the forums but I haven't found anything
helpful yet.
"Mary Chipman [MSFT]" wrote:
> How are you linking the tables? You can write DAO/VBA code to pass the
> correctly-delimited table names.
> Frankly, you'd be better off just changing the names to conform to
> SQLS identifier rules. Having non-compliant names is just going to
> cause more headaches down the road. Take the hit now before you've
> deployed the app.
> -mary
> On Fri, 22 Jun 2007 07:54:04 -0700, didub
> <didub@.discussions.microsoft.com> wrote:
>
|||As I recommended earlier, write code so that you can specify the
delimiters. If you're using UI tools then you have no way of knowing
what the unspoken assumptions are - i.e., what is being passed to ODBC
and then the server. Another option is to put a Profiler trace on it
and see what the server is receiving from the client. It's hard to
tell from a distance what's actually going on under the covers with an
app, especially if someone else wrote it.
-mary
On Fri, 22 Jun 2007 15:09:01 -0700, didub
<didub@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>I agree that the column names should be changed to satisfy SQL naming rules,
>and I plan to do that, but that is not my first priority.
>This app. was created and deployed several years ago by someone who is no
>longer with the company. On the live server and desktops it is working with
>these invalid names.
>My first objective was to install a copy of the system on my own PC so I can
>take it apart and plan some major changes and bug fixes. So ideally I would
>just like to get my test system working as the live system does.
>My guess is that there are some ODBC related settings that I need to change.
>Or perhaps there is something I need to do on the SQL Server database. I
>have searched Knowledgebase and the forums but I haven't found anything
>helpful yet.
>
>"Mary Chipman [MSFT]" wrote:
end linked by ODBC to a SQL Server 2005 back end. (Originally the data was
in an Access database but was later moved to SQL Server 2005 by the Upsizing
tools.)
Some tables have column names which do not conform to the rules given in SQL
Books Online - there are field names with embedded spaces, first character
not a-z or A-Z, name contains '/' and two names which are T-SQL reserved
words. When the tables are viewed via Management Studio, these 'odd' names
are enclosed in square brackets.
The production system is working in this state, but when I try to set up a
test environment on a stand-alone PC, I cannot access these tables. If I try
to link them I get 'ODBC -- Call failed', and if I try to import them I get
error messages about various column names. I can only link to, or import
other tables which do not have these 'odd' field names. If I rename the
columns in SQL server then I can import or link them with no problem.
(My PC has the latest service packs for SQL Server 2005 and Office 2003, and
MDAC 2.8 SP1.)
Somehow the production system works with this data but my test PC doesn't.
What do I need to do on my test PC to use this data with the original 'odd'
column names?
How are you linking the tables? You can write DAO/VBA code to pass the
correctly-delimited table names.
Frankly, you'd be better off just changing the names to conform to
SQLS identifier rules. Having non-compliant names is just going to
cause more headaches down the road. Take the hit now before you've
deployed the app.
-mary
On Fri, 22 Jun 2007 07:54:04 -0700, didub
<didub@.discussions.microsoft.com> wrote:
>I have been asked to maintain an Access 2000 database which is a code front
>end linked by ODBC to a SQL Server 2005 back end. (Originally the data was
>in an Access database but was later moved to SQL Server 2005 by the Upsizing
>tools.)
>Some tables have column names which do not conform to the rules given in SQL
>Books Online - there are field names with embedded spaces, first character
>not a-z or A-Z, name contains '/' and two names which are T-SQL reserved
>words. When the tables are viewed via Management Studio, these 'odd' names
>are enclosed in square brackets.
>The production system is working in this state, but when I try to set up a
>test environment on a stand-alone PC, I cannot access these tables. If I try
>to link them I get 'ODBC -- Call failed', and if I try to import them I get
>error messages about various column names. I can only link to, or import
>other tables which do not have these 'odd' field names. If I rename the
>columns in SQL server then I can import or link them with no problem.
>(My PC has the latest service packs for SQL Server 2005 and Office 2003, and
>MDAC 2.8 SP1.)
>Somehow the production system works with this data but my test PC doesn't.
>What do I need to do on my test PC to use this data with the original 'odd'
>column names?
|||I agree that the column names should be changed to satisfy SQL naming rules,
and I plan to do that, but that is not my first priority.
This app. was created and deployed several years ago by someone who is no
longer with the company. On the live server and desktops it is working with
these invalid names.
My first objective was to install a copy of the system on my own PC so I can
take it apart and plan some major changes and bug fixes. So ideally I would
just like to get my test system working as the live system does.
My guess is that there are some ODBC related settings that I need to change.
Or perhaps there is something I need to do on the SQL Server database. I
have searched Knowledgebase and the forums but I haven't found anything
helpful yet.
"Mary Chipman [MSFT]" wrote:
> How are you linking the tables? You can write DAO/VBA code to pass the
> correctly-delimited table names.
> Frankly, you'd be better off just changing the names to conform to
> SQLS identifier rules. Having non-compliant names is just going to
> cause more headaches down the road. Take the hit now before you've
> deployed the app.
> -mary
> On Fri, 22 Jun 2007 07:54:04 -0700, didub
> <didub@.discussions.microsoft.com> wrote:
>
|||As I recommended earlier, write code so that you can specify the
delimiters. If you're using UI tools then you have no way of knowing
what the unspoken assumptions are - i.e., what is being passed to ODBC
and then the server. Another option is to put a Profiler trace on it
and see what the server is receiving from the client. It's hard to
tell from a distance what's actually going on under the covers with an
app, especially if someone else wrote it.
-mary
On Fri, 22 Jun 2007 15:09:01 -0700, didub
<didub@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>I agree that the column names should be changed to satisfy SQL naming rules,
>and I plan to do that, but that is not my first priority.
>This app. was created and deployed several years ago by someone who is no
>longer with the company. On the live server and desktops it is working with
>these invalid names.
>My first objective was to install a copy of the system on my own PC so I can
>take it apart and plan some major changes and bug fixes. So ideally I would
>just like to get my test system working as the live system does.
>My guess is that there are some ODBC related settings that I need to change.
>Or perhaps there is something I need to do on the SQL Server database. I
>have searched Knowledgebase and the forums but I haven't found anything
>helpful yet.
>
>"Mary Chipman [MSFT]" wrote:
Invalid identifier/column names after Upsize Access data to SQL Se
I have been asked to maintain an Access 2000 database which is a code front
end linked by ODBC to a SQL Server 2005 back end. (Originally the data was
in an Access database but was later moved to SQL Server 2005 by the Upsizing
tools.)
Some tables have column names which do not conform to the rules given in SQL
Books Online - there are field names with embedded spaces, first character
not a-z or A-Z, name contains '/' and two names which are T-SQL reserved
words. When the tables are viewed via Management Studio, these 'odd' names
are enclosed in square brackets.
The production system is working in this state, but when I try to set up a
test environment on a stand-alone PC, I cannot access these tables. If I try
to link them I get 'ODBC -- Call failed', and if I try to import them I get
error messages about various column names. I can only link to, or import
other tables which do not have these 'odd' field names. If I rename the
columns in SQL server then I can import or link them with no problem.
(My PC has the latest service packs for SQL Server 2005 and Office 2003, and
MDAC 2.8 SP1.)
Somehow the production system works with this data but my test PC doesn't.
What do I need to do on my test PC to use this data with the original 'odd'
column names?How are you linking the tables? You can write DAO/VBA code to pass the
correctly-delimited table names.
Frankly, you'd be better off just changing the names to conform to
SQLS identifier rules. Having non-compliant names is just going to
cause more headaches down the road. Take the hit now before you've
deployed the app.
-mary
On Fri, 22 Jun 2007 07:54:04 -0700, didub
<didub@.discussions.microsoft.com> wrote:
>I have been asked to maintain an Access 2000 database which is a code front
>end linked by ODBC to a SQL Server 2005 back end. (Originally the data was
>in an Access database but was later moved to SQL Server 2005 by the Upsizin
g
>tools.)
>Some tables have column names which do not conform to the rules given in SQ
L
>Books Online - there are field names with embedded spaces, first character
>not a-z or A-Z, name contains '/' and two names which are T-SQL reserved
>words. When the tables are viewed via Management Studio, these 'odd' names
>are enclosed in square brackets.
>The production system is working in this state, but when I try to set up a
>test environment on a stand-alone PC, I cannot access these tables. If I tr
y
>to link them I get 'ODBC -- Call failed', and if I try to import them I get
>error messages about various column names. I can only link to, or import
>other tables which do not have these 'odd' field names. If I rename the
>columns in SQL server then I can import or link them with no problem.
>(My PC has the latest service packs for SQL Server 2005 and Office 2003, an
d
>MDAC 2.8 SP1.)
>Somehow the production system works with this data but my test PC doesn't.
>What do I need to do on my test PC to use this data with the original 'odd'
>column names?sql
end linked by ODBC to a SQL Server 2005 back end. (Originally the data was
in an Access database but was later moved to SQL Server 2005 by the Upsizing
tools.)
Some tables have column names which do not conform to the rules given in SQL
Books Online - there are field names with embedded spaces, first character
not a-z or A-Z, name contains '/' and two names which are T-SQL reserved
words. When the tables are viewed via Management Studio, these 'odd' names
are enclosed in square brackets.
The production system is working in this state, but when I try to set up a
test environment on a stand-alone PC, I cannot access these tables. If I try
to link them I get 'ODBC -- Call failed', and if I try to import them I get
error messages about various column names. I can only link to, or import
other tables which do not have these 'odd' field names. If I rename the
columns in SQL server then I can import or link them with no problem.
(My PC has the latest service packs for SQL Server 2005 and Office 2003, and
MDAC 2.8 SP1.)
Somehow the production system works with this data but my test PC doesn't.
What do I need to do on my test PC to use this data with the original 'odd'
column names?How are you linking the tables? You can write DAO/VBA code to pass the
correctly-delimited table names.
Frankly, you'd be better off just changing the names to conform to
SQLS identifier rules. Having non-compliant names is just going to
cause more headaches down the road. Take the hit now before you've
deployed the app.
-mary
On Fri, 22 Jun 2007 07:54:04 -0700, didub
<didub@.discussions.microsoft.com> wrote:
>I have been asked to maintain an Access 2000 database which is a code front
>end linked by ODBC to a SQL Server 2005 back end. (Originally the data was
>in an Access database but was later moved to SQL Server 2005 by the Upsizin
g
>tools.)
>Some tables have column names which do not conform to the rules given in SQ
L
>Books Online - there are field names with embedded spaces, first character
>not a-z or A-Z, name contains '/' and two names which are T-SQL reserved
>words. When the tables are viewed via Management Studio, these 'odd' names
>are enclosed in square brackets.
>The production system is working in this state, but when I try to set up a
>test environment on a stand-alone PC, I cannot access these tables. If I tr
y
>to link them I get 'ODBC -- Call failed', and if I try to import them I get
>error messages about various column names. I can only link to, or import
>other tables which do not have these 'odd' field names. If I rename the
>columns in SQL server then I can import or link them with no problem.
>(My PC has the latest service packs for SQL Server 2005 and Office 2003, an
d
>MDAC 2.8 SP1.)
>Somehow the production system works with this data but my test PC doesn't.
>What do I need to do on my test PC to use this data with the original 'odd'
>column names?sql
Invalid File DSN
Please help me.
Recently I have been getting the following error more and more often:
Microsoft OLE DB Provider for ODBC Drivers error '80004005'
General error: Invalid file dsn 'C:\Program Files\Common Files\ODBC\Data
Sources\"name of dsn"
This doesn't occur all the time jsut every now and then, but like I said
this has been happening more often now. If i run an IISRESET on the web
server making the call to the SQL server the error goes away and everything
works fine. I have done some research and everything I have found so far
says not to use File DSNs. However, the web server has over 60 sites on it
and every single one uses a file DSN or two. I am not the developer so I
can not force them to change their coding only make suggestions, but they
don't really like the suggestion to remove FIle DSNs and make calls
directly. If anyone has any other suggestions PLEASE!! let me know.
--sean.
Unfortunately, that's the price you pay with DSNs -- they often end up
being more trouble than they're worth. If you can prevail on your
developers to use direct connection strings instead, you'll all be
much happier in the long run. Valid ODBC connection strings can be
found at www.able-consulting.com/ADO_Conn.htm and
www.connectionstrings.com.
--Mary
On Tue, 8 Feb 2005 15:30:10 -0500, "Sean Kirby"
<sean.kirby@.blazenet.com> wrote:
>Please help me.
>Recently I have been getting the following error more and more often:
>Microsoft OLE DB Provider for ODBC Drivers error '80004005'
>General error: Invalid file dsn 'C:\Program Files\Common Files\ODBC\Data
>Sources\"name of dsn"
>This doesn't occur all the time jsut every now and then, but like I said
>this has been happening more often now. If i run an IISRESET on the web
>server making the call to the SQL server the error goes away and everything
>works fine. I have done some research and everything I have found so far
>says not to use File DSNs. However, the web server has over 60 sites on it
>and every single one uses a file DSN or two. I am not the developer so I
>can not force them to change their coding only make suggestions, but they
>don't really like the suggestion to remove FIle DSNs and make calls
>directly. If anyone has any other suggestions PLEASE!! let me know.
>--sean.
>
Recently I have been getting the following error more and more often:
Microsoft OLE DB Provider for ODBC Drivers error '80004005'
General error: Invalid file dsn 'C:\Program Files\Common Files\ODBC\Data
Sources\"name of dsn"
This doesn't occur all the time jsut every now and then, but like I said
this has been happening more often now. If i run an IISRESET on the web
server making the call to the SQL server the error goes away and everything
works fine. I have done some research and everything I have found so far
says not to use File DSNs. However, the web server has over 60 sites on it
and every single one uses a file DSN or two. I am not the developer so I
can not force them to change their coding only make suggestions, but they
don't really like the suggestion to remove FIle DSNs and make calls
directly. If anyone has any other suggestions PLEASE!! let me know.
--sean.
Unfortunately, that's the price you pay with DSNs -- they often end up
being more trouble than they're worth. If you can prevail on your
developers to use direct connection strings instead, you'll all be
much happier in the long run. Valid ODBC connection strings can be
found at www.able-consulting.com/ADO_Conn.htm and
www.connectionstrings.com.
--Mary
On Tue, 8 Feb 2005 15:30:10 -0500, "Sean Kirby"
<sean.kirby@.blazenet.com> wrote:
>Please help me.
>Recently I have been getting the following error more and more often:
>Microsoft OLE DB Provider for ODBC Drivers error '80004005'
>General error: Invalid file dsn 'C:\Program Files\Common Files\ODBC\Data
>Sources\"name of dsn"
>This doesn't occur all the time jsut every now and then, but like I said
>this has been happening more often now. If i run an IISRESET on the web
>server making the call to the SQL server the error goes away and everything
>works fine. I have done some research and everything I have found so far
>says not to use File DSNs. However, the web server has over 60 sites on it
>and every single one uses a file DSN or two. I am not the developer so I
>can not force them to change their coding only make suggestions, but they
>don't really like the suggestion to remove FIle DSNs and make calls
>directly. If anyone has any other suggestions PLEASE!! let me know.
>--sean.
>
Monday, March 19, 2012
Invalid File DSN
Please help me.
Recently I have been getting the following error more and more often:
Microsoft OLE DB Provider for ODBC Drivers error '80004005'
General error: Invalid file dsn 'C:\Program Files\Common Files\ODBC\Data
Sources\"name of dsn"
This doesn't occur all the time jsut every now and then, but like I said
this has been happening more often now. If i run an IISRESET on the web
server making the call to the SQL server the error goes away and everything
works fine. I have done some research and everything I have found so far
says not to use File DSNs. However, the web server has over 60 sites on it
and every single one uses a file DSN or two. I am not the developer so I
can not force them to change their coding only make suggestions, but they
don't really like the suggestion to remove FIle DSNs and make calls
directly. If anyone has any other suggestions PLEASE!! let me know.
--sean.Unfortunately, that's the price you pay with DSNs -- they often end up
being more trouble than they're worth. If you can prevail on your
developers to use direct connection strings instead, you'll all be
much happier in the long run. Valid ODBC connection strings can be
found at www.able-consulting.com/ADO_Conn.htm and
www.connectionstrings.com.
--Mary
On Tue, 8 Feb 2005 15:30:10 -0500, "Sean Kirby"
<sean.kirby@.blazenet.com> wrote:
>Please help me.
>Recently I have been getting the following error more and more often:
>Microsoft OLE DB Provider for ODBC Drivers error '80004005'
>General error: Invalid file dsn 'C:\Program Files\Common Files\ODBC\Data
>Sources\"name of dsn"
>This doesn't occur all the time jsut every now and then, but like I said
>this has been happening more often now. If i run an IISRESET on the web
>server making the call to the SQL server the error goes away and everything
>works fine. I have done some research and everything I have found so far
>says not to use File DSNs. However, the web server has over 60 sites on it
>and every single one uses a file DSN or two. I am not the developer so I
>can not force them to change their coding only make suggestions, but they
>don't really like the suggestion to remove FIle DSNs and make calls
>directly. If anyone has any other suggestions PLEASE!! let me know.
>--sean.
>
Recently I have been getting the following error more and more often:
Microsoft OLE DB Provider for ODBC Drivers error '80004005'
General error: Invalid file dsn 'C:\Program Files\Common Files\ODBC\Data
Sources\"name of dsn"
This doesn't occur all the time jsut every now and then, but like I said
this has been happening more often now. If i run an IISRESET on the web
server making the call to the SQL server the error goes away and everything
works fine. I have done some research and everything I have found so far
says not to use File DSNs. However, the web server has over 60 sites on it
and every single one uses a file DSN or two. I am not the developer so I
can not force them to change their coding only make suggestions, but they
don't really like the suggestion to remove FIle DSNs and make calls
directly. If anyone has any other suggestions PLEASE!! let me know.
--sean.Unfortunately, that's the price you pay with DSNs -- they often end up
being more trouble than they're worth. If you can prevail on your
developers to use direct connection strings instead, you'll all be
much happier in the long run. Valid ODBC connection strings can be
found at www.able-consulting.com/ADO_Conn.htm and
www.connectionstrings.com.
--Mary
On Tue, 8 Feb 2005 15:30:10 -0500, "Sean Kirby"
<sean.kirby@.blazenet.com> wrote:
>Please help me.
>Recently I have been getting the following error more and more often:
>Microsoft OLE DB Provider for ODBC Drivers error '80004005'
>General error: Invalid file dsn 'C:\Program Files\Common Files\ODBC\Data
>Sources\"name of dsn"
>This doesn't occur all the time jsut every now and then, but like I said
>this has been happening more often now. If i run an IISRESET on the web
>server making the call to the SQL server the error goes away and everything
>works fine. I have done some research and everything I have found so far
>says not to use File DSNs. However, the web server has over 60 sites on it
>and every single one uses a file DSN or two. I am not the developer so I
>can not force them to change their coding only make suggestions, but they
>don't really like the suggestion to remove FIle DSNs and make calls
>directly. If anyone has any other suggestions PLEASE!! let me know.
>--sean.
>
Invalid Descriptor Index on SQL 2005 sp 1
We have an app that use ODBC and works on SQL server 2000 but
when running the same app and same ODBC driver on 2005 sp 1 we get
Invalid Descriptor Index
Why?
Regards,
DavidMaybe if you show us the actual code that is causing the issue we could make
a more informed answer.
Andrew J. Kelly SQL MVP
"David@.StreamServe" <david.svennevid@.gmail.com> wrote in message
news:1147860037.905325.193680@.j55g2000cwa.googlegroups.com...
> We have an app that use ODBC and works on SQL server 2000 but
> when running the same app and same ODBC driver on 2005 sp 1 we get
> Invalid Descriptor Index
>
> Why?
> Regards,
> David
>
when running the same app and same ODBC driver on 2005 sp 1 we get
Invalid Descriptor Index
Why?
Regards,
DavidMaybe if you show us the actual code that is causing the issue we could make
a more informed answer.
Andrew J. Kelly SQL MVP
"David@.StreamServe" <david.svennevid@.gmail.com> wrote in message
news:1147860037.905325.193680@.j55g2000cwa.googlegroups.com...
> We have an app that use ODBC and works on SQL server 2000 but
> when running the same app and same ODBC driver on 2005 sp 1 we get
> Invalid Descriptor Index
>
> Why?
> Regards,
> David
>
Invalid Cursor State
After I create a table, if I attempt to modify or insert a column using the
wizard in EM, I get the following error:
-Unable to modify table.
ODBC error: [Microsoft][ODBC SQL Server Driver]Invalid Cursor State
I have SP3a installed, Analysis Services and SQL Reporting. Any suggestions?
Thanks.
DanSounds like this KB article.
FIX: An invalid cursor state occurs after you apply Hotfix 8.00.0859 or
later in SQL Server 2000
http://support.microsoft.com/kb/831997
However, this MS PSS only fix looks like BUILD 876. BUILD 878 is public and
located here:
http://support.microsoft.com/?kbid=838166
Since these are cumulative, it would include the fix for the other.
Sincerely,
Anthony Thomas
"DLS" <DLS@.discussions.microsoft.com> wrote in message
news:2BB9D7A0-6BCE-426F-9375-7D205280F4DA@.microsoft.com...
After I create a table, if I attempt to modify or insert a column using the
wizard in EM, I get the following error:
-Unable to modify table.
ODBC error: [Microsoft][ODBC SQL Server Driver]Invalid Cursor State
I have SP3a installed, Analysis Services and SQL Reporting. Any suggestions?
Thanks.
Dan
wizard in EM, I get the following error:
-Unable to modify table.
ODBC error: [Microsoft][ODBC SQL Server Driver]Invalid Cursor State
I have SP3a installed, Analysis Services and SQL Reporting. Any suggestions?
Thanks.
DanSounds like this KB article.
FIX: An invalid cursor state occurs after you apply Hotfix 8.00.0859 or
later in SQL Server 2000
http://support.microsoft.com/kb/831997
However, this MS PSS only fix looks like BUILD 876. BUILD 878 is public and
located here:
http://support.microsoft.com/?kbid=838166
Since these are cumulative, it would include the fix for the other.
Sincerely,
Anthony Thomas
"DLS" <DLS@.discussions.microsoft.com> wrote in message
news:2BB9D7A0-6BCE-426F-9375-7D205280F4DA@.microsoft.com...
After I create a table, if I attempt to modify or insert a column using the
wizard in EM, I get the following error:
-Unable to modify table.
ODBC error: [Microsoft][ODBC SQL Server Driver]Invalid Cursor State
I have SP3a installed, Analysis Services and SQL Reporting. Any suggestions?
Thanks.
Dan
Invalid cursor state
Problem with dsigning tables. when changing datatype, size
etc'
i get message:
ODBC error: [Microsoft][ODBC SQL Server Driver]Invalid
cursor state
microsoft is reffering to: http://support.microsoft.com/?
kbid=831997
but there is nothing there that can fix the problem
what can i do to fix it?
Thankseran,shalom
Check out if the log file is full, what is recovery model of the log file?
<eranv@.gat.co.il> wrote in message
news:369601c48812$bb6d5530$a301280a@.phx.gbl...
> Problem with dsigning tables. when changing datatype, size
> etc'
> i get message:
> ODBC error: [Microsoft][ODBC SQL Server Driver]Invalid
> cursor state
> microsoft is reffering to: http://support.microsoft.com/?
> kbid=831997
> but there is nothing there that can fix the problem
> what can i do to fix it?
> Thanks|||Uri hi and thanks for responding,
The log file is not full and the mode is set to "simple"
this error occurs on all tables and in every database. I
think it has something to do with hotfix or patch that we
installed after sp3a
we are working around that problem by recreating the
tables everytime a change is needed. you can imagin how
hard it is to work like that.
thanks again
Eran
.
>--Original Message--
>eran,shalom
>Check out if the log file is full, what is recovery model
of the log file?
>
><eranv@.gat.co.il> wrote in message
>news:369601c48812$bb6d5530$a301280a@.phx.gbl...
>> Problem with dsigning tables. when changing datatype,
size
>> etc'
>> i get message:
>> ODBC error: [Microsoft][ODBC SQL Server Driver]Invalid
>> cursor state
>> microsoft is reffering to:
http://support.microsoft.com/?
>> kbid=831997
>> but there is nothing there that can fix the problem
>> what can i do to fix it?
>> Thanks
>
>.
>|||Eran
I see, have you looked at http://support.microsoft.com/?kbid=821334
Do you have the same MDAC on the client and server?
<anonymous@.discussions.microsoft.com> wrote in message
news:acf101c48834$30264d70$a601280a@.phx.gbl...
> Uri hi and thanks for responding,
> The log file is not full and the mode is set to "simple"
> this error occurs on all tables and in every database. I
> think it has something to do with hotfix or patch that we
> installed after sp3a
> we are working around that problem by recreating the
> tables everytime a change is needed. you can imagin how
> hard it is to work like that.
> thanks again
> Eran
> .
>
> >--Original Message--
> >eran,shalom
> >Check out if the log file is full, what is recovery model
> of the log file?
> >
> >
> ><eranv@.gat.co.il> wrote in message
> >news:369601c48812$bb6d5530$a301280a@.phx.gbl...
> >> Problem with dsigning tables. when changing datatype,
> size
> >> etc'
> >> i get message:
> >> ODBC error: [Microsoft][ODBC SQL Server Driver]Invalid
> >> cursor state
> >>
> >> microsoft is reffering to:
> http://support.microsoft.com/?
> >> kbid=831997
> >> but there is nothing there that can fix the problem
> >> what can i do to fix it?
> >>
> >> Thanks
> >
> >
> >.
> >|||yes the MDAC versions are the same. the error message
occurs also when working directly on the server.
a general search led me to http://support.microsoft.com/?
kbid=831997
and i think that the link discribes an issue somewhat
relevant, however i could not find a workaround or hotfix
to correct the problem.
>--Original Message--
>Eran
>I see, have you looked at http://support.microsoft.com/?
kbid=821334
>Do you have the same MDAC on the client and server?
>
><anonymous@.discussions.microsoft.com> wrote in message
>news:acf101c48834$30264d70$a601280a@.phx.gbl...
>> Uri hi and thanks for responding,
>> The log file is not full and the mode is set to "simple"
>> this error occurs on all tables and in every database. I
>> think it has something to do with hotfix or patch that
we
>> installed after sp3a
>> we are working around that problem by recreating the
>> tables everytime a change is needed. you can imagin how
>> hard it is to work like that.
>> thanks again
>> Eran
>> .
>>
>> >--Original Message--
>> >eran,shalom
>> >Check out if the log file is full, what is recovery
model
>> of the log file?
>> >
>> >
>> ><eranv@.gat.co.il> wrote in message
>> >news:369601c48812$bb6d5530$a301280a@.phx.gbl...
>> >> Problem with dsigning tables. when changing datatype,
>> size
>> >> etc'
>> >> i get message:
>> >> ODBC error: [Microsoft][ODBC SQL Server Driver]
Invalid
>> >> cursor state
>> >>
>> >> microsoft is reffering to:
>> http://support.microsoft.com/?
>> >> kbid=831997
>> >> but there is nothing there that can fix the problem
>> >> what can i do to fix it?
>> >>
>> >> Thanks
>> >
>> >
>> >.
>> >
>
>.
>|||Eran
You may want to delete the hotfix and re-install sp3.
<anonymous@.discussions.microsoft.com> wrote in message
news:ad1f01c4883a$cd180280$a601280a@.phx.gbl...
> yes the MDAC versions are the same. the error message
> occurs also when working directly on the server.
> a general search led me to http://support.microsoft.com/?
> kbid=831997
> and i think that the link discribes an issue somewhat
> relevant, however i could not find a workaround or hotfix
> to correct the problem.
> >--Original Message--
> >Eran
> >I see, have you looked at http://support.microsoft.com/?
> kbid=821334
> >Do you have the same MDAC on the client and server?
> >
> >
> ><anonymous@.discussions.microsoft.com> wrote in message
> >news:acf101c48834$30264d70$a601280a@.phx.gbl...
> >> Uri hi and thanks for responding,
> >> The log file is not full and the mode is set to "simple"
> >> this error occurs on all tables and in every database. I
> >> think it has something to do with hotfix or patch that
> we
> >> installed after sp3a
> >> we are working around that problem by recreating the
> >> tables everytime a change is needed. you can imagin how
> >> hard it is to work like that.
> >> thanks again
> >> Eran
> >> .
> >>
> >>
> >> >--Original Message--
> >> >eran,shalom
> >> >Check out if the log file is full, what is recovery
> model
> >> of the log file?
> >> >
> >> >
> >> ><eranv@.gat.co.il> wrote in message
> >> >news:369601c48812$bb6d5530$a301280a@.phx.gbl...
> >> >> Problem with dsigning tables. when changing datatype,
> >> size
> >> >> etc'
> >> >> i get message:
> >> >> ODBC error: [Microsoft][ODBC SQL Server Driver]
> Invalid
> >> >> cursor state
> >> >>
> >> >> microsoft is reffering to:
> >> http://support.microsoft.com/?
> >> >> kbid=831997
> >> >> but there is nothing there that can fix the problem
> >> >> what can i do to fix it?
> >> >>
> >> >> Thanks
> >> >
> >> >
> >> >.
> >> >
> >
> >
> >.
> >
etc'
i get message:
ODBC error: [Microsoft][ODBC SQL Server Driver]Invalid
cursor state
microsoft is reffering to: http://support.microsoft.com/?
kbid=831997
but there is nothing there that can fix the problem
what can i do to fix it?
Thankseran,shalom
Check out if the log file is full, what is recovery model of the log file?
<eranv@.gat.co.il> wrote in message
news:369601c48812$bb6d5530$a301280a@.phx.gbl...
> Problem with dsigning tables. when changing datatype, size
> etc'
> i get message:
> ODBC error: [Microsoft][ODBC SQL Server Driver]Invalid
> cursor state
> microsoft is reffering to: http://support.microsoft.com/?
> kbid=831997
> but there is nothing there that can fix the problem
> what can i do to fix it?
> Thanks|||Uri hi and thanks for responding,
The log file is not full and the mode is set to "simple"
this error occurs on all tables and in every database. I
think it has something to do with hotfix or patch that we
installed after sp3a
we are working around that problem by recreating the
tables everytime a change is needed. you can imagin how
hard it is to work like that.
thanks again
Eran
.
>--Original Message--
>eran,shalom
>Check out if the log file is full, what is recovery model
of the log file?
>
><eranv@.gat.co.il> wrote in message
>news:369601c48812$bb6d5530$a301280a@.phx.gbl...
>> Problem with dsigning tables. when changing datatype,
size
>> etc'
>> i get message:
>> ODBC error: [Microsoft][ODBC SQL Server Driver]Invalid
>> cursor state
>> microsoft is reffering to:
http://support.microsoft.com/?
>> kbid=831997
>> but there is nothing there that can fix the problem
>> what can i do to fix it?
>> Thanks
>
>.
>|||Eran
I see, have you looked at http://support.microsoft.com/?kbid=821334
Do you have the same MDAC on the client and server?
<anonymous@.discussions.microsoft.com> wrote in message
news:acf101c48834$30264d70$a601280a@.phx.gbl...
> Uri hi and thanks for responding,
> The log file is not full and the mode is set to "simple"
> this error occurs on all tables and in every database. I
> think it has something to do with hotfix or patch that we
> installed after sp3a
> we are working around that problem by recreating the
> tables everytime a change is needed. you can imagin how
> hard it is to work like that.
> thanks again
> Eran
> .
>
> >--Original Message--
> >eran,shalom
> >Check out if the log file is full, what is recovery model
> of the log file?
> >
> >
> ><eranv@.gat.co.il> wrote in message
> >news:369601c48812$bb6d5530$a301280a@.phx.gbl...
> >> Problem with dsigning tables. when changing datatype,
> size
> >> etc'
> >> i get message:
> >> ODBC error: [Microsoft][ODBC SQL Server Driver]Invalid
> >> cursor state
> >>
> >> microsoft is reffering to:
> http://support.microsoft.com/?
> >> kbid=831997
> >> but there is nothing there that can fix the problem
> >> what can i do to fix it?
> >>
> >> Thanks
> >
> >
> >.
> >|||yes the MDAC versions are the same. the error message
occurs also when working directly on the server.
a general search led me to http://support.microsoft.com/?
kbid=831997
and i think that the link discribes an issue somewhat
relevant, however i could not find a workaround or hotfix
to correct the problem.
>--Original Message--
>Eran
>I see, have you looked at http://support.microsoft.com/?
kbid=821334
>Do you have the same MDAC on the client and server?
>
><anonymous@.discussions.microsoft.com> wrote in message
>news:acf101c48834$30264d70$a601280a@.phx.gbl...
>> Uri hi and thanks for responding,
>> The log file is not full and the mode is set to "simple"
>> this error occurs on all tables and in every database. I
>> think it has something to do with hotfix or patch that
we
>> installed after sp3a
>> we are working around that problem by recreating the
>> tables everytime a change is needed. you can imagin how
>> hard it is to work like that.
>> thanks again
>> Eran
>> .
>>
>> >--Original Message--
>> >eran,shalom
>> >Check out if the log file is full, what is recovery
model
>> of the log file?
>> >
>> >
>> ><eranv@.gat.co.il> wrote in message
>> >news:369601c48812$bb6d5530$a301280a@.phx.gbl...
>> >> Problem with dsigning tables. when changing datatype,
>> size
>> >> etc'
>> >> i get message:
>> >> ODBC error: [Microsoft][ODBC SQL Server Driver]
Invalid
>> >> cursor state
>> >>
>> >> microsoft is reffering to:
>> http://support.microsoft.com/?
>> >> kbid=831997
>> >> but there is nothing there that can fix the problem
>> >> what can i do to fix it?
>> >>
>> >> Thanks
>> >
>> >
>> >.
>> >
>
>.
>|||Eran
You may want to delete the hotfix and re-install sp3.
<anonymous@.discussions.microsoft.com> wrote in message
news:ad1f01c4883a$cd180280$a601280a@.phx.gbl...
> yes the MDAC versions are the same. the error message
> occurs also when working directly on the server.
> a general search led me to http://support.microsoft.com/?
> kbid=831997
> and i think that the link discribes an issue somewhat
> relevant, however i could not find a workaround or hotfix
> to correct the problem.
> >--Original Message--
> >Eran
> >I see, have you looked at http://support.microsoft.com/?
> kbid=821334
> >Do you have the same MDAC on the client and server?
> >
> >
> ><anonymous@.discussions.microsoft.com> wrote in message
> >news:acf101c48834$30264d70$a601280a@.phx.gbl...
> >> Uri hi and thanks for responding,
> >> The log file is not full and the mode is set to "simple"
> >> this error occurs on all tables and in every database. I
> >> think it has something to do with hotfix or patch that
> we
> >> installed after sp3a
> >> we are working around that problem by recreating the
> >> tables everytime a change is needed. you can imagin how
> >> hard it is to work like that.
> >> thanks again
> >> Eran
> >> .
> >>
> >>
> >> >--Original Message--
> >> >eran,shalom
> >> >Check out if the log file is full, what is recovery
> model
> >> of the log file?
> >> >
> >> >
> >> ><eranv@.gat.co.il> wrote in message
> >> >news:369601c48812$bb6d5530$a301280a@.phx.gbl...
> >> >> Problem with dsigning tables. when changing datatype,
> >> size
> >> >> etc'
> >> >> i get message:
> >> >> ODBC error: [Microsoft][ODBC SQL Server Driver]
> Invalid
> >> >> cursor state
> >> >>
> >> >> microsoft is reffering to:
> >> http://support.microsoft.com/?
> >> >> kbid=831997
> >> >> but there is nothing there that can fix the problem
> >> >> what can i do to fix it?
> >> >>
> >> >> Thanks
> >> >
> >> >
> >> >.
> >> >
> >
> >
> >.
> >
Invalid Cursor State
After I create a table, if I attempt to modify or insert a column using the
wizard in EM, I get the following error:
-Unable to modify table.
ODBC error: [Microsoft][ODBC SQL Server Driver]Invalid Cursor State
I have SP3a installed, Analysis Services and SQL Reporting. Any suggestions?
Thanks.
DanSounds like this KB article.
FIX: An invalid cursor state occurs after you apply Hotfix 8.00.0859 or
later in SQL Server 2000
http://support.microsoft.com/kb/831997
However, this MS PSS only fix looks like BUILD 876. BUILD 878 is public and
located here:
http://support.microsoft.com/?kbid=838166
Since these are cumulative, it would include the fix for the other.
Sincerely,
Anthony Thomas
--
"DLS" <DLS@.discussions.microsoft.com> wrote in message
news:2BB9D7A0-6BCE-426F-9375-7D205280F4DA@.microsoft.com...
After I create a table, if I attempt to modify or insert a column using the
wizard in EM, I get the following error:
-Unable to modify table.
ODBC error: [Microsoft][ODBC SQL Server Driver]Invalid Cursor State
I have SP3a installed, Analysis Services and SQL Reporting. Any suggestions?
Thanks.
Dan
wizard in EM, I get the following error:
-Unable to modify table.
ODBC error: [Microsoft][ODBC SQL Server Driver]Invalid Cursor State
I have SP3a installed, Analysis Services and SQL Reporting. Any suggestions?
Thanks.
DanSounds like this KB article.
FIX: An invalid cursor state occurs after you apply Hotfix 8.00.0859 or
later in SQL Server 2000
http://support.microsoft.com/kb/831997
However, this MS PSS only fix looks like BUILD 876. BUILD 878 is public and
located here:
http://support.microsoft.com/?kbid=838166
Since these are cumulative, it would include the fix for the other.
Sincerely,
Anthony Thomas
--
"DLS" <DLS@.discussions.microsoft.com> wrote in message
news:2BB9D7A0-6BCE-426F-9375-7D205280F4DA@.microsoft.com...
After I create a table, if I attempt to modify or insert a column using the
wizard in EM, I get the following error:
-Unable to modify table.
ODBC error: [Microsoft][ODBC SQL Server Driver]Invalid Cursor State
I have SP3a installed, Analysis Services and SQL Reporting. Any suggestions?
Thanks.
Dan
Monday, March 12, 2012
Invalid Cursor State
After I create a table, if I attempt to modify or insert a column using the
wizard in EM, I get the following error:
-Unable to modify table.
ODBC error: [Microsoft][ODBC SQL Server Driver]Invalid Cursor State
I have SP3a installed, Analysis Services and SQL Reporting. Any suggestions?
Thanks.
Dan
Sounds like this KB article.
FIX: An invalid cursor state occurs after you apply Hotfix 8.00.0859 or
later in SQL Server 2000
http://support.microsoft.com/kb/831997
However, this MS PSS only fix looks like BUILD 876. BUILD 878 is public and
located here:
http://support.microsoft.com/?kbid=838166
Since these are cumulative, it would include the fix for the other.
Sincerely,
Anthony Thomas
"DLS" <DLS@.discussions.microsoft.com> wrote in message
news:2BB9D7A0-6BCE-426F-9375-7D205280F4DA@.microsoft.com...
After I create a table, if I attempt to modify or insert a column using the
wizard in EM, I get the following error:
-Unable to modify table.
ODBC error: [Microsoft][ODBC SQL Server Driver]Invalid Cursor State
I have SP3a installed, Analysis Services and SQL Reporting. Any suggestions?
Thanks.
Dan
wizard in EM, I get the following error:
-Unable to modify table.
ODBC error: [Microsoft][ODBC SQL Server Driver]Invalid Cursor State
I have SP3a installed, Analysis Services and SQL Reporting. Any suggestions?
Thanks.
Dan
Sounds like this KB article.
FIX: An invalid cursor state occurs after you apply Hotfix 8.00.0859 or
later in SQL Server 2000
http://support.microsoft.com/kb/831997
However, this MS PSS only fix looks like BUILD 876. BUILD 878 is public and
located here:
http://support.microsoft.com/?kbid=838166
Since these are cumulative, it would include the fix for the other.
Sincerely,
Anthony Thomas
"DLS" <DLS@.discussions.microsoft.com> wrote in message
news:2BB9D7A0-6BCE-426F-9375-7D205280F4DA@.microsoft.com...
After I create a table, if I attempt to modify or insert a column using the
wizard in EM, I get the following error:
-Unable to modify table.
ODBC error: [Microsoft][ODBC SQL Server Driver]Invalid Cursor State
I have SP3a installed, Analysis Services and SQL Reporting. Any suggestions?
Thanks.
Dan
Friday, March 9, 2012
Invalid character value for cast specification error
I'm using Access 2K via ODBC to replicated SQL Server 2K. In some tables (not all) when I try to add a record either with a form or directly in the datasheet I get this error message and all form controls/table cells display '#Name?'. The record is added
and displays correctly if I close and reopen the form/table. I can add records with no problem in Enterprise Manager.
Any help gratefully received.
Jonathan Attree
Hi, I am getting exactly the same problem although this problem has only occurred since I implemented merge replication. Does anyone have an answer?
Amanda
and displays correctly if I close and reopen the form/table. I can add records with no problem in Enterprise Manager.
Any help gratefully received.
Jonathan Attree
Hi, I am getting exactly the same problem although this problem has only occurred since I implemented merge replication. Does anyone have an answer?
Amanda
Friday, February 24, 2012
Intersolv ODBC Driver
Help me!
I try to import some data from an informix 5.0 table to Sql Server 2000 with
a DTS package.
I use Intersolv ODBC driver version 03.011.0021 to connect to the database.
It works well, but i can't define a parameter in the sql statement. For
example if a try to execute :
select *
from table
where field = ?
The dts environment give me an "unspecified syntax error...."
Where is the problem?
The driver don't support parameters or these must be defined with another
syntax?
Bye
DanieleCan you post a code snippet?
SQL Server T-SQL doesn't support anything close to that syntax so I'm not
sure what you're doing exactly...
From T-SQL, you would need to build dynamic SQL or use sp_exectutesql to do
the parameterization you're talking about.
Brian Moran
Principal Mentor
Solid Quality Learning
SQL Server MVP
http://www.solidqualitylearning.com
"Nonno Oreste" <dffdfd@.dfd.dfd> wrote in message
news:OSsw2unuDHA.1596@.TK2MSFTNGP10.phx.gbl...
with
database.
I try to import some data from an informix 5.0 table to Sql Server 2000 with
a DTS package.
I use Intersolv ODBC driver version 03.011.0021 to connect to the database.
It works well, but i can't define a parameter in the sql statement. For
example if a try to execute :
select *
from table
where field = ?
The dts environment give me an "unspecified syntax error...."
Where is the problem?
The driver don't support parameters or these must be defined with another
syntax?
Bye
DanieleCan you post a code snippet?
SQL Server T-SQL doesn't support anything close to that syntax so I'm not
sure what you're doing exactly...
From T-SQL, you would need to build dynamic SQL or use sp_exectutesql to do
the parameterization you're talking about.
Brian Moran
Principal Mentor
Solid Quality Learning
SQL Server MVP
http://www.solidqualitylearning.com
"Nonno Oreste" <dffdfd@.dfd.dfd> wrote in message
news:OSsw2unuDHA.1596@.TK2MSFTNGP10.phx.gbl...
quote:
> Help me!
> I try to import some data from an informix 5.0 table to Sql Server 2000
with
quote:
> a DTS package.
> I use Intersolv ODBC driver version 03.011.0021 to connect to the
database.
quote:
> It works well, but i can't define a parameter in the sql statement. For
> example if a try to execute :
> select *
> from table
> where field = ?
> The dts environment give me an "unspecified syntax error...."
> Where is the problem?
> The driver don't support parameters or these must be defined with another
> syntax?
> Bye
> Daniele
>
Subscribe to:
Posts (Atom)