Because I want to be able to revert to FMP 13 in case I have problems, I created a new folder with copies of my.
Filemaker pro alternatives no cd#
I bought a license from this reseller yesterday (I used accumulated American Express points, so my out-of-pocket expense was $7.68), and installed FMP 16.0.5 (from a download there's no CD for this "point release") last night. I realized I was in the same boat as the OP FileMaker Pro 13 is not 64-bit and is not compatible with macOS 10.14 Mojave-which I haven't installed yet.Īfter taking one look at the price for FMP 17 and picking myself up off the floor, I Googled for purchasable one-user Filemaker Pro 16. After I recently made my first change to any report in at least 5 years, I started worrying. Needless to say this has only one user on one computer. I have an FMP database for keeping track of sales for guitar method books, which I originally built from a sample application around 2004 for my guitar teacher and later took over-along with the business-shortly before he died.
Filemaker pro alternatives software#
It's not something I've ever needed to do, so I have no idea when it happened, but the software simply locks up if you attempt to extract the data in any alternative format.Ĭould I get away with picking up an older (cheaper) version of FMP? Presumably, this will still leave me with the impending 32/64bit problem but might let me dump the data to a format I can then import into different software? Are there any current software packages costing less than half a grand that would let me work with legacy FMP files?Īny thoughts/recommendations much appreciated. To complicate things, at some point during the previous years, the export facility in my version seems to have been broken, presumably by an OS incompatibility. It's just that the current version of FileMaker appears to be well over £500. I think I started out in FMP 3 or 4… at some point, I upgraded to 9, which is where it's been ever since and now I'm starting to get warnings about impending incompatibility… none of which I'm complaining about. I also liked the relational thing of being able to hold contact info in a separate DB and propagate it through multiple records in the invoicing DB, and so on… I'm not going to pretend that this was ever an optimal solution, but a couple of the companies I worked for through the 90s were heavily FMP-based, so it was what I knew.
My current billing/invoicing system is all built around FMP databases I created myself about a decade ago.
0 kommentar(er)
