well ... maybe the are ...

try to add an "order by 1,2,3 " at the sqlserver side as wel as at the access side.

Maybe then you'll see the data is...

- is that database configured "autoclose on" ?

- if yes, it needs a restore-step to be opened again.

(keep in mind SSMS doesn't autorefresh the object-browser pane)

- is your sqlserver "member" object a view or a table ?

If it is a view, can you post the ddl ?

-Are you using a linked table to...

did you check http://www.sqlservercentral.com/Forums/Topic459602-148-1.aspx ?

or

http://www.sqlservercentral.com/Forums/FindPost328227.aspx

or http://www.sqlservercentral.com/articles/OpenDataSource/61552/

or http://www.sqlservercentral.com/Forums/Topic475347-8-1.aspx

I'm glad you found the issue and were able to fix it.

You could also have granted full control or the service account to the folder that contains the logfiles.

But that...

The little test ...

/*

use master

alter database SSC_TestBU set read_only with rollback immediate;

drop database SSC_TestBU;

alter database SSC_TestRcvr set read_only with rollback immediate;

drop database SSC_TestRcvr;

...

- What do you use to read the xls file ?

- did you try using DTS ?

- keep your head cool ( if you don't, no one else will do it for you !)

- have a look a sqlserver errorlog file and search for anomalies

- take...

- off course you cannot apply previous log-backups to the new full backup.

- every full backup starts a new recovery "cycle".

- For SQL2005 there is this new "copy_only" parameter that...

Especialy in that case, put it in a effective .net application or SSIS package and don't poison your db-server with it !

Prepare the...

you may want to have a look at fn_split kind of functions .

Maybe they may provide what you look for without using dynamic sql.

have a look at :

http://www.sqlservercentral.com/scripts/Miscellaneous/30225/

http://www.sqlservercentral.com/scripts/String+Manipulation/61509/

Is someone using the "copy database" wizard ?

It proposes a "detach - attach" scenario. :sick:

Be happy it's only the clr going down.

I've had a whole instance going down when activating a memory hog CLR function.

http://www.sqlservercentral.com/Forums/FindPost457289.aspx

IMO This is one of the reasons to avoid CLR...

This is the way we implemented it ...

http://www.sqlservercentral.com/articles/Security/3203/

maybe that can be a good starting point for you..

Why materialize it in two tables ?

- I prefer small objects

- Adaptability.