Dec 23
dp FM as data bridge: A field-mapping challenge
FM as data bridge: A field-mapping challenge
I continue with the project of developing a FileMaker bridge between
two different data systems. ODBC is problematic for a number of
reasons that don't need to be explained here. The method of choice for
both systems is import/export. Each of the data sources is most
comfortable with a Matching Field Names type of import, but they use
different field names for the same data (FirstName vs. Name_First). As
tedious as I find field-mapping in FM, it's actually easier than in
either of the other two systems. My current plan is to build an FM
solution consisting of Table A, which contains field names and data
from the first source, and Table B which contains the field names and
data from the second source. I will then map an import from A to B,
and another import from B to A. Then I will try to tie it together
with scripts to make the procedure as automatic as possible. Can
anyone suggest a more efficient (and less tedious) way to accomplish
this objective?
Thanks,
dp
--
This list is a free service of LassoSoft: http://www.LassoSoft.com/
Search the list archives: http://www.ListSearch.com/FileMaker/Browse/
Manage your subscription: http://www.ListSearch.com/FileMaker/
Dec 23
Jonathan Fletcher Re: FM as data bridge: A field-mapping challenge
Dec 23, 2009; 10:43
Jonathan Fletcher
Re: FM as data bridge: A field-mapping challenge
Dec 23
Jonathan Fletcher Re: FM as data bridge: A field-mapping challenge
Dec 23, 2009; 10:43
Jonathan Fletcher
Re: FM as data bridge: A field-mapping challenge
Dec 23
Michael Gilman Re: FM as data bridge: A field-mapping challenge
Dec 23, 2009; 10:49
Michael Gilman
Re: FM as data bridge: A field-mapping challenge
Dec 24
dp Re: FM as data bridge: A field-mapping challenge
Re: FM as data bridge: A field-mapping challenge