Results 1 to 3 of 3
  1. #1
    Mercator is offline Novice
    Windows 7 64bit Access 2010 64bit
    Join Date
    Dec 2012
    Posts
    10

    Move to SharePoint and multivalue fields?

    Hi All:



    Does anyone know if using multivalue lookup fields in an Access Web Database cause issues when moving to SharePoint? The Compatibility Checker is error free, but when publishing the web database to SharePoint, I receive errors about attachment fields, which I do not have in my web database as far as I know. The only additions I have made was adding 4 lookup fields that allowed multivalues per the end-users' requests.

    Thanks,
    Merc

  2. #2
    June7's Avatar
    June7 is online now VIP
    Windows XP Access 2010 32bit
    Join Date
    May 2011
    Location
    The Great Land
    Posts
    52,816
    Interesting, I thought multi-value feature was created because of Sharepoint and web database. So you had a working database under Sharepoint before those new fields? You set the lookups in table?

    Want to provide the web and non-web versions of db for analysis? Follow instructions at bottom of my post.
    How to attach file: http://www.accessforums.net/showthread.php?t=70301 To provide db: copy, remove confidential data, run compact & repair, zip w/Windows Compression.

  3. #3
    Mercator is offline Novice
    Windows 7 64bit Access 2010 64bit
    Join Date
    Dec 2012
    Posts
    10
    Yes, I had created an original version with 17 Lookup fields. This was published to SharePoint with a Main Navigation form and two subforms (one for entering data, and per the users' requests a datasheet form so it would "look like Excel"). During the revision phase, four more lookups were requested. At this point I have determined that I am only allowed 20 lookup fields (until the lookup throttling is changed), and it seems like, saving a sharepoint access database as a local copy to republish, is riddled with problems if my lookup tables had any special characters in them, and users had populated the forms. (the original published database had blank forms and no data entered, it works well on SharePoint until saving as a local db for publishing to a different sharepoint). As I muddle through this, I'll post what I find out so other people; hopefully, won't have to deal with this too. It would be nice if the Compatibility Checker would actually catch data problems not just schema problems, that is what has puzzled me because the Compatibility Checker shows no errors with all of this.

Please reply to this thread with any new information or opinions.

Similar Threads

  1. Move to SharePoint Site issues
    By Mercator in forum SharePoint
    Replies: 4
    Last Post: 12-27-2012, 05:52 PM
  2. How to display multivalue fields
    By Trojnfn in forum Access
    Replies: 5
    Last Post: 10-22-2012, 03:48 PM
  3. Replies: 0
    Last Post: 03-09-2012, 07:04 AM
  4. Move all access 2003 data to sharepoint 2010
    By accesstosharepoint in forum SharePoint
    Replies: 0
    Last Post: 10-22-2011, 08:32 AM
  5. Move fields to the right in a report
    By degras in forum Reports
    Replies: 1
    Last Post: 01-20-2011, 08:40 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Other Forums: Microsoft Office Forums