anything in your error logs similar to?

2008-10-10 08:49:14.66 Server * BEGIN STACK DUMP:

2008-10-10 08:49:14.66 Server * 10/10/08 08:49:14...

Sounds like you may have some runaway tasks. Check sys.dm_os_schedulers for cpu_id 7 and the current_tasks_count and sys.dm_os_tasks for task_state, sys.dm_os_waiting_tasks for blocking_session_id etc

The movie TRON!

try this, substituting where specific

CREATE TABLE PDFImageTest (account_num integer,image_data VARBINARY(MAX));

DECLARE @AccountNum integer

SET @AccountNum = 2456789

INSERT INTO PDFImageTest (account_num,image_data)

SELECT @accountNum,image_data

FROM OPENROWSET(BULK N'C:\Backup\Disk Usage by Top Tables - 6262008 441...

However, you could create an empty database on the 2000 box, script all your objects in the 2005 database and apply against the 2000 database, then copy the data using...

Garbage In = Garbage Out

Your form can have a recordsource which could be anything from a table, view or a procedure. On this form you may have multiple subforms, combo boxes, list boxes etc....

You can use ADO in much the same way you would coding a VB front end. A good reference is http://msdn.microsoft.com/en-us/library/ms675104(VS.85).aspx and also

http://msdn.microsoft.com/en-us/library/aa189885(office.10).aspx although it is...

I would suggest the fastest and most useful way to learn how to use an adp project would be to create a project from scratch, connect it to an existing...

I guess it depends upon how hacked the code in the Access database is whether it would be complex to migrate to an adp. I too have worked in Access...

Steve

Of course a .NET application may be the ultimate goal but there is no reason any Access.mdb database could not be migrated to an adp with minimal effort. The adp...

You are absolutely correct. Write module level code using ADO and use an Access .adp Project, NOT linked tables or .mdb file. Use Access only for you forms and reports....