Our system predates me by a big chunk and I have been tasked to make a report about it for the new Chair. I'm trying to be factual but I have only pieces of info and I need to extrapolate the story. Trying to reconstruct the timeline. To be sure I don't put my foot in my mouth, I need to verify a few things. I seek answers for the two questions in blue. Thank you!!
Our system was likely developed between 1997 and 1999. The first record was for our fiscal year 1999/2000. So I assume it was either in the format .fp3 or .fp5. I have no idea what version of client or server they had. I don't think it is relevant.
The database was upgraded in 2004 to the format .fp7
When I started working on it in 2015, we were working with the client FileMaker Pro 9.0v3
Our hosted services provider told me that the Server was FM7 << Is that possible?
Summer 2016, when I migrated it to FM15 I had to first recover the files with the FM 9 client to convert it to the .fmp12 format and then recover these converted versions with the FM 15 client.
What I am trying to place is the attempt to upgrade to FM10. My boss does not remember exactly when so lets say 2009.
My boss mentionned something about Windows Server 2007 and something about not being able to read the file, and unstability... << What do you think went wrong?
This failed attempt to upgrade is actually one of the key factors that prompted the (debacle) move to CRM Dynamics in 2014: they were under the impression that our old DB was not upgradable and that new Windows Servers would not support older versions. Since we needed new Servers for our other office technology needs, such as Outlook Exchange, the operating system situation needed to be addressed. The rational became: if money has to be injected into building a new one, a reevaluation of the platform is warranted. My boss had concerns about the long term survival of FileMaker; our hosted services provider favoured Microsoft products and the limits of their experience with FileMaker was to read the information provided for the server install as well as the releases notes.
One of the amazing things this forum allows is to come, take the time to organize your thoughts to ask a "respondable" question.
The side effect is that you grow in the process. Thanks to the simple fact that the forum exists, people read the post and all of that created hope and drive. Here is today's work that kickstarted from the above post...
First Part: Timeline
1997-1999 Development of the COMPANY database management system on the FileMaker platform. Likely deployed at the start of the fiscal year 1999/2000 in the format .fp5.
2004 – Database system upgrade to the FileMaker 7 platform in the new .fp7 format, running on Microsoft Server 2003.
2008 or 2009? – The COMPANY’s “server” (a home grade machine converted for business needs) dies and XYZ Consulting is called in to build a professional machine to support all of the COMPANY’s technology needs which include emailing, printers, database, etc. The chosen server licence is Microsoft Small Business Server 2007 (SBS 2007) a bundled type server.
2009 – Unsuccessful attempt to upgrade the database system to version FM Server 10 onto the SBS 2007. The SBS 2007 isn’t one of the three Windows Servers recommended as compatible by FileMaker. As a work around, XYZ Consulting deploys onto the SBS 2007 machine a virtual Microsoft Server 2003 to be able to continue to run FM Server 7.
2013 – The COMPANY contracts with ABCD, a managed hosted services provider. Henceforth, the SBS 2007 runs as one hosted virtual server and the Ms Server 2003 runs as another hosted virtual server.
2013 – Microsoft announces Ms Server 2003 end of life (EOL) date for July 14, 2015. That means that no more security patches will be released and that the product will no longer be supported.
Comment:
At this time, for the COMPANY, as it understands it, the EOL of Ms Server 2003 means the EOL of the COMPANY database. This is because the 2009 failed attempt to upgrade has led COMPANY’s management to assume that its database, still running onto the FM Server 7, is not upgradable.
This assumption is critical but not factual in 2009 and even less in 2013.
For one part, FM Servers need to be installed on their own server; it is not clear if the service pack 2 (SP2) was installed on the virtual Window Server 2003 or if the edition was the right one recommended by FileMaker for compatibility.
For the other part, it is likely that the upgrade was not done correctly. Database files cannot just be copied onto the new upgraded server. They have to be recovered on a client first, then uploaded onto the server from a client, preferably a FileMaker Pro Advanced client.
Nevertheless, it is with that assumption in mind that COMPANY management devises how to handle that technology issue. At that point, the rationale is: “our database is doomed and since money has to be injected into building a new database system, a revaluation of the platform is warranted.”
COMPANY’s management has concerns about the long-term survival of FileMaker as a company. For its part, when consulted, our hosted services provider favours Microsoft products.
And it continues for 4 more pages...