Pages containing 'Fileman'
To say that File Manager is VISTA's database management system is a gross understatement, so gross that it is more misleading than helpful.
Traditional database systems run side by side with the applications, offering data-related services (like creating, reading, updating, and deleting records - the services with the unattractive acronym CRUD - along with many, many other such services). In other words, most DBMSes have a peer-to-peer relationship with the applications that use them to manage their data.
One of the two top strategic goals for FLAP Phase One (which ran from October 2012 through March 2013) was code convergence, to create a shared, common Fileman codebase that all VISTA dialects could run, to maximize our ability to exchange data and software with one another, to ensure that innovations anywhere became innovations everywhere as quickly as possible, and to reduce the amount of reinventing the wheel we had to do.
The main VISTA dialects we aimed at converging for Phase One were:
1) VA VISTA
2) IHS RPMS
3) WorldVistA EHR
4) vxVistA, and
FLAP Phase Two began yesterday - Sunday, 23 November 2014 - with the launching of a Preparatory stage.
In its 1.1 release, FMQL will move its JSON format over to JSON-LD. This form of JSON provides a straightforward JSON with rigorous semantics, something key for VistA data with its large and powerful data model.
I am please to announce that I finished writing a Fileman tutorial for programming students that I promised Luis Ibañez. Here it is.
Thank you Luis for the impetus, and sorry it took so long.
FLAP Worker Bee
We got more reader feedback (thank you!), so here is an updated version of the Getting Started Manual. Hopefully this is also the final version.
We are now working on the Security Manual, and hope to have it available by the end of February.
We will use the new peer review checklist to walk through peer review for FileMan 22.2 in the OTJ. Peer review checklist is at:
Update: We had a very successful consensus review of Fileman 22.2 during yesterday's meeting. Based on the meeting, we have the following two actions that need to be investigated, after which we will submit a recommendation via the peer review: