Question Problem with a database

[rc-alex]

Hello,

I am in quite a situation. I need a database for a handful of users spread accross the country. I also need there to be no issues with conflicting edits.

I thought this would be solved by using a Web Database with SharePoint Access services in SharePoint 2010.

However, I cannot find any way to create sums, percentages, or charts in Access Services web databases. Since we are going to use this to create reports of the results, the whole database is now apparenty useless.

How can I create this same database in a regular (non-Web-database) format but still easily share it without using an intranet, and also avoid conflicting writes? I have the SharePoint site to post it to, if that helps.

I need to have this up preferrably tomorrow (Thursday) but latest friday and I have a good bit of work left to do and I still don't know how to approach.

Thank you!!

 

[Guus2005]

For starters it is very strange that you can't create sums etc. It is part of any regular SQL statement in any dialect by using a GROUP BY clause.

Sharepoint Access Services doesn't support VBA code so you must use macro's for anything you want to do. Good luck with that.

Alternatives:
You could use replication
You could use a GUID (global unique identifier) as PK id's instead of the autonumber field to create a unique identifier for a record. Consolidating the databases doesn't give you any PK conflicts.

 

[rc-alex]

Hello,
In my research since last night, I believe I found an option that might work well. I can "move the database to SharePoint" with Access, and all of the tables will become lists. The database is stored on SharePoint and users save a local copy of the database. However, entries to the DB tables are immediately entered into the SharePoint lists so all users see the updates when they sync back. The forms and reports are still run from Access. Any issues with this method? The only issue I potentially see right now is whether or not reports will have the latest data by other users, or if the user has to manually sync right before running a report. But that shouldn't be a major issue in this case.

Any major issues I may be overlooking?

Thanks.
Alex

 

[Guus2005]

Looks like you got it all figured out.

Thanks for getting back with a solution!