...and replying to my own previous message, now when I use "Find in Design" I 
get a dialog pop up twice with the message:

"One field was bad. It has been suppressed from your form."

Having this come up every time is going to be a PITA :(( Is there a way to fix 
this?

Regards,
 
Narinder Chandi,
ToolBox Systems Ltd.
-- 

-----Original Message-----
From: 4D_Tech <[email protected]> on behalf of 4D Tech Mailing List 
<[email protected]>
Reply-To: 4D Tech Mailing List <[email protected]>
Date: Sunday, 1 September 2019 at 20:34
To: 4D Tech Mailing List <[email protected]>
Cc: Narinder Chandi <[email protected]>
Subject: Re: Check Orphan Forms Warnings in MSC

    Thanks Tim - I overlooked that!
    
    So, repairing the structure eliminated the previous FO4D warnings but I now 
have 9 new ones under Check Project Forms:
    
    ___Orphan___31086.Page1.Picture1 uses a deprecated picture format: PICT.
    ___Orphan___31086.Page1.Picture2 uses a deprecated picture format: PICT.
    ___Orphan___31086.Page1.Picture3 uses a deprecated picture format: PICT.
    ___Orphan___31086.Page1.Picture4 uses a deprecated picture format: PICT.
    ___Orphan___31086.Page1.Picture5 uses a deprecated picture format: PICT.
    ___Orphan___31086.Page1.Picture6 uses a deprecated picture format: PICT.
    ___Orphan___31086.Page1.Picture7 uses a deprecated picture format: PICT.
    ___Orphan___31086.Page1.Picture8 uses a deprecated picture format: PICT.
    ___Orphan___31086.Page1.Picture9 uses a deprecated picture format: PICT.
    
    Any ideas on how to find and/or remove these?
    
    Regards,
     
    Narinder Chandi,
    ToolBox Systems Ltd.
    -- 
    
    -----Original Message-----
    From: 4D_Tech <[email protected]> on behalf of 4D Tech Mailing 
List <[email protected]>
    Reply-To: 4D Tech Mailing List <[email protected]>
    Date: Sunday, 1 September 2019 at 20:13
    To: 4D Tech Mailing List <[email protected]>
    Cc: Tim Nevels <[email protected]>
    Subject: Re: Check Orphan Forms Warnings in MSC
    
        On Sep 1, 2019, at 2:00 PM, Narinder Chandi  wrote:
        
        > So, after a long, long hard slog migrating from v15 to v17, I have 
reduced the 6,000 MSC warnings down to the last 2.
        > 
        > Under "Check Orphan Forms" I am seeing:
        > The form resource FO4D of id 31086 is not used anywhere
        > The form resource FO4D of id 21169 is not used anywhere
        > 
        > How do I address these? I know probably I can just ignore them but it 
would be nice to have zero warnings! I have tried without success:
        > * compacting the structure
        > * delete the .4DIndy structure index file followed by compacting the 
structure
        > 
        > Any other suggestions gratefully received!
        
        
        Did  you do a “repair” of the structure?  Not “compact”, but “repair”.
        
        Tim
        
        *****************************************
        Tim Nevels
        Innovative Solutions
        785-749-3444
        [email protected]
        *****************************************
        
        **********************************************************************
        4D Internet Users Group (4D iNUG)
        Archive:  http://lists.4d.com/archives.html
        Options: https://lists.4d.com/mailman/options/4d_tech
        Unsub:  mailto:[email protected]
        **********************************************************************
    
    
    **********************************************************************
    4D Internet Users Group (4D iNUG)
    Archive:  http://lists.4d.com/archives.html
    Options: https://lists.4d.com/mailman/options/4d_tech
    Unsub:  mailto:[email protected]
    **********************************************************************


**********************************************************************
4D Internet Users Group (4D iNUG)
Archive:  http://lists.4d.com/archives.html
Options: https://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:[email protected]
**********************************************************************

Reply via email to