|
I struggled with this problem for a long time before someone on the
list gave me some good advice, which seems to have resolved the
problem. If the FMP source has any "ghost" fields still present on a
layout, even though the field has since been deleted, the editor
crashes when defining that particular datasource. This could be a
layout other than the one you are trying to define (even if you're only
planning to use "layout 0"), and you'll still have the problem. You
really need to find and remove "all" of these ghost fields from all
your layouts. I did this on several different occasions and it solved
the problem each time. Hope this helps... Dave Lubovinsky Carnegie Mellon University Pittsburgh, PA Wayne Irvine wrote: Jane Olivera at [EMAIL PROTECTED] wrote: ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf |
- Re: Witango-Talk: Bad FMP datasource Wayne Irvine
- Re: Witango-Talk: Bad FMP datasource Dave Lubovinsky
- Re: Witango-Talk: Bad FMP datasource Wayne Irvine
- Re: Witango-Talk: Bad FMP datasource Dan Stein
