A manager created an issued database (based on a template) and asked me to write some code that would create new records based on incoming emails. The code is run on the Outlook side, fired by the Item_Added event of the Inbox Collection.
Everything was working fine until the manager, on a lark, published the DB to Sharepoint. Now, if the database is open when the Outlook event fires, he gets Error 3045 - file already in use. if the database is NOT open, it works just fine.
He's not desperate for the db to be on sharepoint, so I simply created a new database and imported everything from the non-working one, and now everything is back to functioning normally.
So this raises two questions:
1) If a user pubilshes the database to Sharepoint, why would the local copy be locked when opened (as though it were open in exclusive mode, which it wasn't - I checked)?
and
2) Is there any way to revert the local copy of the database that's been published to share point back to its old state?
Everything was done in Access 2007, Outlook 2007 and Sharepoint 2010. I know virtually nothing about Sharepoint - I still develop primarily in Client/Server environments.
Everything was working fine until the manager, on a lark, published the DB to Sharepoint. Now, if the database is open when the Outlook event fires, he gets Error 3045 - file already in use. if the database is NOT open, it works just fine.
He's not desperate for the db to be on sharepoint, so I simply created a new database and imported everything from the non-working one, and now everything is back to functioning normally.
So this raises two questions:
1) If a user pubilshes the database to Sharepoint, why would the local copy be locked when opened (as though it were open in exclusive mode, which it wasn't - I checked)?
and
2) Is there any way to revert the local copy of the database that's been published to share point back to its old state?
Everything was done in Access 2007, Outlook 2007 and Sharepoint 2010. I know virtually nothing about Sharepoint - I still develop primarily in Client/Server environments.
