I've asked this question in a number of Access forums without any response, so I thought I'd try it here as I believe it may be a performance issue with SharePoint.

I have an Access 2010 database that is updated from a SharePoint list using a macro that deletes the current table in Access, then imports a list SharePoint 2007 site.

Intermittently, but quite often, when I attempt to do the import I get a popup that presents "Operation is not supported for this type of object."  When this happens I just start over (and over) and if I'm lucky it only takes two or three times before the import begins to happen.  If I'm really lucky it won't "stop working" and I'll get all my data imported.

Any ideas where to look for the cause of this problem.? I believe it has to do with the SP server and nothing at all to do with A

Hi run4it,

I am trying to involve someone familiar with this topic to further look at this issue.

Thanks,
Daniel Yang
Forum Support
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

Hi run4it,

if i may ask, are there other users that able to do the same process with you regarding this issue?

just to make sure, because seems there is a limitation on the threshold and throttling regarding the connectivity.

http://technet.microsoft.com/en-us/library/cc262787#ListLibrary

but anyway, did you see any error messages in ULS log, or by fiddler, it may give some clue.

please have a check if should you have cascade delete also, if you have the feature, then perhaps you may try to increase it: Together with the CascadeDeleteTimeoutMultiplier property, the CascadeDeleteMaximumItemLimit property controlsthe duration of a short-term Web site lock that is taken to perform referential integrity delete operations. The duration of the short-term Web site lock is calculated as follows in milliseconds:CascadeDeleteTimeoutMultiplier * CascadeDeleteMaximumItemLimit.

$webapp.CascadeDeleteMaximumItemLimit = 10000

$webapp. CascadeDeleteTimeoutMultiplier = 1200

$webapp.Update()

are those properties configurable in MOSS 2007?

Also - There is one primary user .  She receives the error, as I do when I work in there to develop things (such as the reports) for her.    I've had two other people test the import and they receive the error

if the number of items present in the list exceeds the list threshold then you should try :

1. to import your data through a SSIS package or

2. to create a view in the list to limit the number of items and to mergethe data obtained with the existent data. I use the merging method with success whilst extracting data from list with more than 80.000 items in SharePoint 2007.

Or perhaps the size of the list does not make the solution viable anymore for Access and it is time to get to next step meaning a better database like SQL Server and a proper interface like a desktop / web application.

The list is currently at 4300.  I do not expect that it will exceed 5,000.  While new items are added regularly, there are many that are flagged as "removed".  It is my intention to create a workflow that will archive these to another list.

I have someone in my development group who worked on an SSIS import for me yesterday and was not successful.  He kept getting a message about failure to import - something about data loss in a particular column.  I don't know the specifics, but it didn't seem to make any sense for the circumstances.

Data loss can be handled or ignored depending on the situation but even if items are marked with "Removed" it doesn't mean the number of items from the list is small. Perhaps your macro uses Caml Query to limit the items retrieved from the list.

As for SSIS import it works perfectly with SharePoint lists and I had different types of data imported in the last 3-4 years I used it. These particular list adapters are the holly grail for this kind of operations :

SharePoint List Source and Destination

It occurs to me that I was importing from the All Items view.  I do not need all fields of data to be imported for my three reports.  I'm working on a new view with less data in it and seeing if it helps.

I did  this and it did not appear to help any. Still get error (or not).

Hi run4it,

if i may ask, when you reproduce the issue to import from sharepoint to access, is there any messages in ULS log that stated the error code?

perhaps you can list the steps to reproduce the issue also, so we may check it.

for testing, is it possible to create smaller testing environment and data for testing purpose?

I am having this trouble again. Below is the error. I believe this error is being thrown on the import of the second of two tables that are specified.