>Hi all,
>
>A customer of mine has heavily integrated their VFP app with a document management system (DMS) that I do not maintain. It is basically a PostgreSQL server and then a blob server for the documents. Although the product is current, I am getting longer and longer wait times if my customer wants any changes done e.g. waiting 2 weeks for an email reply is about the norm and now we are about 6 mos. behind on a project. It is not the platform ("Nuxeo") but the fact that the developer/integrator I think has moved on to "bigger and better" things (i.e. larger companies) and there does not seem to be a lot of developers around. It also takes mega bucks each time a new release comes out as it seems Nuxeo changes so many things between releases that we both have to rewrite code.
>
>My customer has said a few times - "could you not just write us something" (to take its place). I don't really want to use VFP to write a document system (although I guess I could). I also don't want them totally reliant on my as I expect to retire in about 5 years.
>
>For the current document platform, they have a REST api which we have used to totally integrate their VFP app with the DMS. When we first started using the project about 8 years ago, I was really busy with them and others so I did not want to learn the API. Instead the other developer created some wrapper procedures on his side that allowed me to make fairly simple calls into the api e.g. "CreateFolder(xx)" and "AddDocument(yy)".
>
>We are now getting to the point of thinking seriously about replacing this system. I would like to move forward with something that is long-term maintainable such as Sharepoint so that even if they replace my VFP app some day, they do not also have to change their document storage.
>
>So has anyone developed with Sharepoint? Has anyone used their api?
>
>Or any other ideas if they are long-term maintainable.
>
>Thanks,


REST API is a great protocol.
You can expose it from a number of platforms.
I'm currently interfacing with 2 and I know the developers of both.
One is written in .NET/SQL Server and the other in PHP/MySQL.

Without knowing the specifics of the application I couldn't recommend one over the other but all things being equal, I'd start with PHP/MySQL (It's free and runs on Linux (also free)








>Albert