ACCESS 2007 and Sharepoint WSS 3.0

[WillemdeNie]

I'm working on migration of my application to a sharepoint.
The frontend is located on some PC's; the backend is migrated to sharepoint tables. It works fine but I have some problems to solve:
Some tables are rather big and this gives a bad performance.

A solution could be: Work off-line and syncronize at the end of the day.

Problem1: This functionality is not available in the runtime version.

Problem 2:If we buy the full version (I would prefer not) the user can choose between "synchronize" and "ignore all changes" The last option is not what we want; but how to prevent the user to make such a mistake?

Possible solutions:
Is it possible to make this "work offline" and "synchronise" from VBA behind a button on a form?

Can we disable the function ignore in the full version?

Any idea for other solutions?

 

[dfenton]

You might want to wait a few months for this, as Sharepoint 2010 has a number of significant performance enhancements that make large Sharepoint lists usable without the massive performance hit.

As to using the runtime, I'm pretty sure the features should still be available with it, but as I've never worked directly with Sharepoint or the runtime (except in trivial senses), I may be wrong. I just don't think there are many things that full Access can do that the runtime cannot except for design changes.

Have you checked to see if there are DoCmd.Runtime commands for replicating the menu commands that control working offline/synchronizing in full Access? If so, those can likely be used in the runtime, as well.

 

[WillemdeNie]

Thanks for responding, but I have still no answers on this issue.
Anybody any idea where to find this information.

I phoned with microsoft and the told me that this is a "professional" question and they do not want to answer for free (although, they should support me for a 90 days
period).

It is a quit big issue for me I have to go live in 5 weeks!
So any ideas?