Setting source table in Import script step?

[MadOverlord]

I've been using FM for decades, so when I decided to do a KickStarter project using FM to build a custom database to track all the backers and fulfillment was a no-brainer (especially since KickStarter's toolset is non-existent and 3rd-party solutions are expensive and limited).

 

The database has actually gotten sophisticated enough that I'm strongly considering releasing (unleashing?) it as a FM application, but I'm having an annoying issue with the Import Script Step

 

One thing I'll have to do for the application is provide an "upgrade from previous version" feature that imports data from an older version into a new one -- I expect that once other people start using the app, I'll have to add functionality (supporting other crowdfunding platforms, and so on). So I need to import the tables from older versions of the database into the current version.

 

The problem is that while the Import script step allows you to specify the source file and destination table you want to import into, and do the obvious field name matching, it doesn't appear to let you specify the source table -- which means the user will have to manually match the source and destination tables, which is not ideal.

 

Is there any way to deal with this? Or is there a better way to do upgrade migration?

 

Really, I'm quite surprised that FM doesn't have an "match fields and import everything" feature.

 

Much obliged for any assistance you can provide.

[GlennS]

Have you had a look at 

 

https://www.goya.com.au/refreshfm

 

Sounds like exactly what you need.

 

But doesn't answer the question, I know