what Guru is saying is you will receive an error if you try and use EXEC to populate a @table variable;you must use a #temp or ##temp table

here's a proc...

we recently did the same thing in our shop...we had separate databases for each application.  whenever one of our clients had more than one application, the issue of duplicate data...

don't know if this will help, but this thread talks about differences in file/folder permissions screwing up an install on a normal machine:

http://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=5&messageid=357952#bm358701

HTH

you cannot do that natively. the change/insert information related to data is not captured.

usually, if this is required,  you'd add two columns to the table, as well as a trigger....search...

this will be data related....

on db1, the recordset frm.AdodcTemp.Recordset was loaded with a select statement...

but on db2, the same select statment returned no data, so the recordset is at the...

you've got almost all the pieces...i've done the same thing as well:

To check Syntax:

SET PARSEONLY ON

-- Execute your query

GO

SET PARSEONLY OFF

To Actual Compile and check for objects existance:

SET NOEXEC ON

GO

--...

isn't it @@proc_id? so object_name(@@proc_id), rather than the @@spid?

i have this handy query stored in my snippets collection.

select name as DBNAME,STATUS,

CASE WHEN (STATUS &         1) = 0 THEN 'FALSE' ELSE 'TRUE' END AS [AUTOCLOSE_(ALTER_DATABASE)],

CASE WHEN (STATUS...

i don't think that error refers to free storage card/disk memory, but rather the amount of RAM that is available to perform the query;

my CE machine has 128M of ram,...

i think this can be fixed simply by adding some code to either the button that submits the data, or the Sub Page_Load event; the page will have all the values that...

No problem Steve; just wanted you to know; i bet it has something to do with the high traffic your site gets; i love this site and spend a lot...

I found it; it's two pieces of the puzzle...it must be a system function, and it ALSO must be owned by 'system_function_schema' ... NOT dbo:

http://msdn2.microsoft.com/en-us/library/aa224829(SQL.80).aspx

SELECT UID FROM master.dbo.sysusers WHERE...

like above, I've never hit a limit on the number of values in the IN() statement, and read it gets converted to a temp table by SQL Server;

I've gotten an error...

definitely not a best practice, i admit...I was just showing by example that just because something is a marked as a system function, does not make it available to ::fn_...

i have been bitten by this bug 6 times this week; some of my posts couldn't have taken me over 3 minutes to type, others were huge detailed answers....I'm a damn decent...