Viewing 5 posts - 1 through 5 (of 5 total)
Did you check the following:
Is the ODBC source a System DSN, not an User DSN? Is the ODBC source on the server machine?
Hope this helps.
Erik
May 26, 2005 at 11:55 pm
You could try to open the recordset in an alternative way:
g_rsData.Open cmdSubCommand, , adOpenStatic, adLockReadOnly
Set g_rsData.ActiveConnection = Nothing
m_lngDataRecordCount = cmdSubCommand.Parameters("@RecordCount")
This does the trick in my applications.
Erik
January 27, 2005 at 11:51 pm
If you search for "column gitter", you will find a few scripts that will do what you want. Given a tablename a series of column lists is generated (columns, declarations,...
January 20, 2005 at 12:12 am
I have had a similar problem with a large first transaction log backup. It turned out that, as part of the maintenance plan, there was a rebuild index step just...
June 3, 2004 at 1:42 am
I found the problem.
Just prior to the full backup I did a rebuild of the indexes (with the sqlmaint utility). This was the reason for the large transaction log...
June 3, 2004 at 1:33 am
Viewing 5 posts - 1 through 5 (of 5 total)