migrate filemaker 6.5 app to 12 - coding requirements? - filemaker

I've been given a request to upgrade an application running under filemaker pro 6.5.
It's connected to some serial devices and uses plugin-component (troi) to solve the communication (rs232).
It's running in a closed network attached to a remote FM65-database.
Will FMP12 be able to run the application w/o a lot of recoding or has things changed too much?
Regards,
/t

Simple answer, yes.
First of, there was no FileMaker 6.5. It went from version 5 to 5.5. to 6 and then 7. When version 7 was released there was a major update in fileformat for the databases, introducing multiple tables in a singel file and a new relationship schema.
Between version 11 and 12 there was another big update in fileformat. The bigest change being that the layouts are now rendered as HTML/CSS using WebKit.
Even though a lot has happend since version 6 FileMaker Inc always try to be backward compatible. As far as I know, no functionality has been removed, at least nothing vital.
Troi Serial Plugin works with FileMaker 12 but you will need to upgrade the plugin. you can read more about the changes for the plugin, pricing and download a demo at
http://www.troi.com/software/serialplugin.html
You can also download a 30 day trail of FileMaker from http://www.filemaker.com
Thus you can easily try the entire setup for free before doing it for production.
The only thing you probably will have to adjust is the function call for the plugin Troi Serial, but that should be easy!
Hope this helps

I'd recommend you use Metadata Magic to analyze the FP5 solution.
There are some script steps that can be problematic when upgrading. This will give you a comprehensive report of what issues to look for and where to find them. It's not uncommon to find script steps that need to be reordered or changed.

Related

System.Reactive for WPF .NET 6

I'm trying to target .NET 6 for my WPF app, but because I'm using RX.net, the highest I can go is net5.0-windows10.0.19041. One example is that ObserveOnDispatcher() is not available when I'm targeting net6.0-windows, which my app makes heavy use of.
Does anybody know either A) when a .NET 6 version of RX.NET will be released, or B) any workarounds for ObserveOnDispatcher() or ObserveOn(DispatcherScheduler.Current.Dispatcher) on .NET 6?
Thanks
A relatively painless way I found was to simply add the ReactiveUI.WPF package to my WPF projects. This allowed me to advance to net6.0-windows, and also to use DispatcherScheduler. I am not using anything from ReactiveUI library, so this is technically a hack, but took 5 minutes of my time and added only a few hundred kilobytes added to the shipped binaries, so it was worth it for me to be able to move on from previously being held back on net5.0-windows10.0.19041 because of RX.
If I had more time and skill I would dig into how the ReactiveUI.WPF source code achieved this desired effect, and apply this to my own source code... maybe someone has a more elegant, non-hack solution.
This will be fixed in v5.1
https://github.com/dotnet/reactive/pull/1660
You could try the nightly builds as per the readme.
https://github.com/dotnet/reactive#get-nightly-builds

Firebirdclient and Select statements are slow for no reason

I have a .Net 4.6.1 Winforms application which has more or less 10 years.
It has worked pretty well since the beginning, but in the last few weeks I faced a problem I never had.
Firebird 2.5 (latest version available)
.net client (latest version available)
Visual studio 2015 or 2019 (in both versions, same problem)
Now, the application, when is about Firebird, calls a sequence of select statements in order to load a dataset. It works well, as usual, as it always worked. Since few weeks, the whole sequence of select statements is slow, tremendously slow.
What do I mean with slow? It usually takes 5 or 6 seconds in my PC to load the whole set of data, now it takes 70 seconds, with no reason. Nothing has changed in the architecture or sequence, nothing was added or removed from the environment.
However, I don't know why, the release version of the software is fast as it was originally, so I don't really get where the point is here.
I have a debug version in Visual Studio which is slow at loading the data using a set of select statements, and a release version which is fast as usual.
Now, when I first realized that the software was running very slow, I upgraded the whole set of Firebird components to the latest versions, but had no joy. I was still using old versions because I had no real reason to upgrade: "does it work? Don't touch it!"
In the release version I use the embedded Firebird version, because I have to redistribute the application. In the debug, the server version, so I can manage the database with IBExpert and run the software together. It has always been like this since ages.
So, I'm looking for a suggestion, because I have no idea where or what to look for.
I fixed this odd behaviour by setting Pooling=true in the connection properties

Movable Type 4 vs 5

I have a Movable Type site running MT 4.38, and I was wondering whether I should upgrade to 5.
For a while, MT 4 and 5 seemed to have been developed concurrently, but now I only see activity in MT 5. Has MT 4 been abandoned?
The person using the site is change averse, so I only want to upgrade if it's absolutely necessary (i.e. security issues).
Thanks
Yes. Movable Type 4.38 has a patch for a security vulnerability which you should be sure to apply. But beyond that, you should absolutely upgrade to Movable Type 5.2.3.
The big reason is that Movable Type 4.38 will be end-of-lifed on December 31, 2013. This means that there will be no security updates for Movable Type 4.38 after that date.
Movable Type 5 has a number of great new features that are huge improvements over MT 4.38:
New and improved Rich Text Editor based on TinyMCE
Revision history on the most-used objects in the CMS
List-management framework enhances Movable Type's ability to manage large amounts of data inside the CMS
Sortable categories and folders
Template tags for things like mt:EntryPrimaryCategory
Enhanced multi-blog support
Huge support improvements for Webkit-based browsers (Safari and Google Chrome) as well as IE 8 and 9
Login failure detection, allowing either account or IP address lock out
With all due respect, no one should be running a version of Movable Type that is no longer supported with security patches. It's foolish to think that any one person can know all of the possible security issues in an older version of a Content Management System such as Movable Type.
Yes, MT4 is no longer developed. It still receive security patchs every few months, but there will not be a new version.
As for what you want to use, MT4 and MT5 have a different set of plugins. So if you want to upgrade, check that the plugins that you need support MT5 or have a MT5 replacement.
Upgrading would work without any problem if you are not using 3rd party plugins.
If you're using 3rd party plugins, you might encounter compatibility issues because the v5.x architecture is much different than 4.x.
Before considering to upgrade to v5.x you may like to check your 3rd party plugins and see if there is a version that works with v5.x.
Another thing to consider is to clone your installation and try to upgrade it on a different domain/folder or on a stage server where you could check that everything works before upgrading your live installation.
Alternatively you could order a professional movable type upgrade service from:
http://www.movabletypeupgrade.com/

How to upgrade OpenERP 5.0 to 6.0

I have an OpenERP 5.0 installation with a few custom modules, that I wish to upgrade to OpenERP 6.0.
I have some experience with this kind of sofware and I have inspected OpenERP. Sadly, I don't have actual experience with OpenERP, and I like to ask for some help in order to avoid mistakes. When researching this, I found there are several strategies (ETL processes, data-upgrade modules)... I assume I'll need to review all custom modules.
What are the guidelines or best practice in order to upgrade an OpenERP 5.0 installation to 6.0?
We're still planning our migration from 5.0 to 6.0, so I don't have any personal experience with the process. We are planning to tackle the work ourselves, but we've done a lot of custom development, so we're pretty comfortable with the OpenERP code. If I were inheriting the system from someone else as it sounds like you are, I would be very tempted by the support contract that includes doing migrations for you.
In addition to the paid service, there also appears to be an open-source tool available for running data migrations. It is also discussed in several forum posts. (There really are a lot.)
Our tentative plans are:
Try out the migration tool for a demo database from plain 5.0 to plain 6.1.
Migrate the code for our custom modules to 6.1, following the Pragtech guidelines.
Extend the migration tool's configuration to cover our custom modules and any others that weren't included with the tool.
Run the migration on our full database into a sandbox and test the heck out of it.
Launch and celebrate!
Update:
We've started our migration process, and we're using OpenUpgrade instead of the Domsense tool. We never really looked at the Domsense tool, so I can't say which is better. I'm very happy with OpenUpgrade so far.
In general, I've found version 6.1 much easier to customize than 5.0 was. So far, I haven't had to change any core modules. For example, most places where a core module inserts a record, it calls a helper method to prepare the data. If you add a new column that you want to be populated, you can just override that helper method. For example, we added a grouping field to several tables and then wanted to copy it from sales order line to stock move. We overrode the sale module's version of sale_order._prepare_order_line_move() with our own version.
I posted a separate question about customizing reports.
The down side is that every customized feature we try to migrate requires some change. So far there has always been a change in the core module that somehow breaks our customization. Either a field name changed, or the screen layout changed, or the whole model name changed. You can usually figure out how to fix it, but everything takes time.
The best approach is to contract an OpenERP Enterprise. Migrating is quite complex and OpenERP can do the job for you. It's a fixed price for unlimited bugfixes and migrations: http://www.openerp.com/catalog/146

Sourcecontrol for Clarion 6

We're still developing a bunch of our application in Clarion 6 Enterprise. I was wondering if anyone knows of a sourcecontrol system that works well with Clarion 6?
I'd be surprised if the standard source control systems weren't just fine, e.g., Subversion. Is there something special about Clarion 6 enterprise?
I believe Rick Martin has tools that allow Clarion to work with subversion and tortise version control systems. They allow you to export the changed procedures to TXA's and import the changes back into the application.
One of the things I like about his system is that when a procedure is checked back into the Source Control System his tools will build a current version of your product so you can verify that the changes don't create compile errors.
The tools are not for sale though. They come with your buying his consulting services.
You're free to rename the modules in Clarion - so you're not bound to the existing generated names.
However that's not the root problem. the root problem is that you don't want to be editing CLW and INC files, you want to be editing the APP file. Otherwise your changes will be lost when the app regenerates.
You can use Subversion, or any other system, with app files - they're just binary files. From a rollback point of view this is fine.
Unfortunately though when you checkout an app you get the whole app. So no one else on the team can work on any other procedures in the app at the same time. If your apps are small then this is no big deal, but if you have a single-app system, or a system comprising of large apps, then it can become a hindrance.
The other disadvantage is that, being a binary file, it's not possible for the version control to merge files together - it's an all-or-nothing situation.
You can also try TDC. It's more than just a VCS for Clarion because you also have a Tracking System.
By the way, TDC is written with Clarion.
Look on Rick Martin presentation it's very useful, but not for sale :(
http://www.clarionlive.com/images/stories/videos/webinar11.wmv