Comments on: Removing unused fields from database

By: joeydog

joeydog — Tue, 15 Feb 2011 16:48:40 +0000

Copy style -c worked – usused fields are gone!

By: joeydog

joeydog — Tue, 15 Feb 2011 16:21:20 +0000

What type of Compact should be used?

By: brooklynegg

brooklynegg — Mon, 27 Oct 2008 14:17:49 +0000

Josenoel: You seem to want two things — keep the fields in records and stop them from appearing in the list of available fields. However, you cannot have both. If you want the field to be removed from the list of fields that can be chosen within Designer, you must remove the field from all forms and subforms, and run an agent that affects every record that has the field that uses @Deletefield to remove it. These are your only options.

Are you trying to describe a way to have a list of “favorite fields” that would be the default list so the common fields are generally available, but keep the other fields in a full list? That would be kind of cool, but it definitely is not a current option. Maybe when Designer is offered within Eclipse someone will write a widget that will provide that function.

If this is offbase, please further clarify your problem so we can address it.

By: stiletto

stiletto — Mon, 20 Oct 2008 14:26:03 +0000

I’m assuming you’re asking about brooklynegg’s comment regarding an agent to delete the field…
Since you know about doing design work, I’ll just tell you that the important command is
FIELD myfieldname := @DeleteField
Create an agent to execute that against all docs, or selected docs that you select.