From: Tom D. <td...@vg...> - 2000-05-03 16:26:28
|
On Tue, 2 May 2000, Larry W. Virden wrote: > The problem with making a copy of the database is that if someone is > memory starved they may not get to make the change. The problem with > making the change directly is that if something goes wrong, the database > is lost... Safety first then. Rebuilds (add/delete fields, change field type) should happen infrequently so asking user to have free memory should not be a major hassle. (If not, they can always hotsync and use desktop utilities to do conversion.) Tom |