Submitting form writes to Access DB for Some Users... not others! - InfoPath Dev
in

InfoPath Dev

Use our Google Custom Search for best site search results.

Submitting form writes to Access DB for Some Users... not others!

Last post 06-10-2009 02:55 PM by Hilary Stoupa. 1 replies.
Page 1 of 1 (2 items)
Sort Posts: Previous Next
  • 06-10-2009 02:40 PM

    Submitting form writes to Access DB for Some Users... not others!

    We are developing a tool for tracking change control that uses InfoPath forms with fairly complex rules, submitting to a few form libraries as well as writing to an Access DB (which will be transitioned to SQL Server.)
     
    We are experiencing an inconsistent issue that has me stumped.
     
    Some users are able to write to the DB and some are not.
    None are getting error messages about this.  
    The best control group for the issue are three test users, CP, CW and MA. They all have the same permissions to the same sharepoint areas, including the site's Shared Documents, where the db currently sits. CW and MA are able to submit, and data is saved to form libraries and the db as expected. When CP submits, everything performs as expected EXCEPT nothing is written to the db.
     

    No error or warning is given related to this, her submissions just don't write to the db but an autonumber Record ID is recorded on the form, what would be the next record in the db! (and she can read data from queries on the db in other forms)

     
    One other test user so far has the same issue as CP.
     
    ... There are no workgroups or security built into the DB itself.... IE setting have been checked for accessing data across domains.
     
    Thanks in advance for your help.
  • 06-10-2009 02:55 PM In reply to

    Re: Submitting form writes to Access DB for Some Users... not others!

    Have you had one of your 'submit successful' users log onto CP's machine and try to submit?

    Hilary Stoupa

Page 1 of 1 (2 items)
Copyright © 2003-2019 Qdabra Software. All rights reserved.
View our Terms of Use.