Might it be as simple as

SET oQryResults = ...

?

I think I have also only ever used the ExecuteWithResultsAndMessages against the server level, never tried against the database level like...

I have not used Visual FoxPro before, but I know I have done this kind of thing with some simple Visual Basic before and maybe you can use these ideas..

I...

If you have done all those steps from the MS site, then the only other thing I have had a problem with before that doesn't appear to be on the...

I agree with John.  What I have typically seen is to enable real-time scanning and if performance is a concern then just set the database files (or Data directory) as exclusions to that...

I don't think you can connect from EM to SQL 2005 - I think you would get an error about needing to connect to SQL 2005 using SMO.  Anyhow, for...

Also for Access databases (mdb's) and outside of anything in EM, I used to just read the Access .ldb file with Notepad and that would list all the workstation names that were connected to my...

I was running SQL 2000 and SQL 2005 on the same server - although I was doing it more for testing purposes - but I did not have any issues. ...

Wow- thanks- I can't believe I never noticed that!

Having transaction log backups with the Simple recovery model doesn't make much sense to me since with Simple you're generally making full backups only (since you can only restore/recover from...

In SQL Server Management Studio connect to your SQL2005 instance.  In Management Studio under that instance right-click on the "Databases" sub-group and choose New Database.  On the General page you'll...

Just to share --

In SQL 2005 Management Studio under Management, Maintenance Plans, right click: I have also create a "New Maintenance Plan"- where there is a Cleanup Backup Task that I can...

I have used the various frequency types as you've found- I usually have set these using SQLDMO.. and I have also gone the route you were thinking originally - where...

I hear you - that makes it more difficult.. without creating seperate cleanup steps for each or adding the step to each existing maintenance plan (and without creating entirely new maintenance plans...

Sounds like you got it.. I was going to say that I do not think "Remote Connections" are enabled by default- part of Microsoft's "Secure by default" mentality these days.

In SQL 2005 you can connect to your SQL server using SQL Server Management Studio.  Right-click on the server (top level), choose Properties.  On the left side click Security.  On the Security...