[AccessD] Form corruption?

[Janet Erbach]

Then I will try testing that to see how many objects I'm able to write
before it blows up....

On Tue, Mar 3, 2015 at 5:22 PM, John W. Colby <jwcolby at gmail.com> wrote:

> Good point.  I think that number is somewhere around 400  IIRC.
>
> John W. Colby
>
>
> On 3/3/2015 6:06 PM, David McAfee wrote:
>
>> Forms are only allowed a limited number of controls over the history of
>> the
>> form itself.
>>
>> Even if they've been deleted.
>>
>> You may be hitting that number.
>>
>> D
>>
>> On Tue, Mar 3, 2015 at 3:02 PM, Janet Erbach <jerbach.db at gmail.com>
>> wrote:
>>
>>  John -
>>>
>>> It's actually not allowing me to ADD new objects.  It will draw objects
>>> up
>>> to a point - and then just crap out.  It chokes on the 'CreateControl'
>>> command.
>>>
>>>
>>> On Tue, Mar 3, 2015 at 4:42 PM, John W. Colby <jwcolby at gmail.com> wrote:
>>>
>>>  Can you trap and ignore the error?  If it is saying that it can't delete
>>>> an object because the object doesn't exist then just ignore the error?
>>>>
>>>> John W. Colby
>>>>
>>>> On 3/3/2015 3:46 PM, Janet Erbach wrote:
>>>>
>>>>  Hello All -
>>>>>
>>>>> My Productivity App from WIFI hell has another component to it that I
>>>>>
>>>> need
>>>
>>>> to ask about.  This portion of the app was written by my co-worker
>>>>>
>>>> using a
>>>
>>>> methodology I did NOT want to employ.  He designed the main form so that
>>>>> 90% of the form objects are *drawn on the form at load time.* Existing
>>>>> objects are deleted first, and then new ones created using
>>>>> 'CreateControl'.
>>>>>
>>>>>
>>>>> This is a 2 page form - page 1 with command buttons and page 2 with
>>>>> what
>>>>> are basically 'hand drawn' charts.  I've attached 2 screen shots to
>>>>> give
>>>>> an
>>>>> idea of the number of objects that are being created.
>>>>>
>>>>> He designed it this way so that there would be, in his mind, the
>>>>>
>>>> ultimate
>>>
>>>> amount of flexibility in terms of drawing a form with 1 group of
>>>>>
>>>> machines
>>>
>>>> or 10 groups of machines.  No objects to hide/activate - just create
>>>>>
>>>> them
>>>
>>>> all from scratch each time.
>>>>>
>>>>> It works pretty well out on the production floor for the most part.
>>>>> But
>>>>> when I'm working in the app, making changes to the code behind the form
>>>>> (or
>>>>> even just making changes to stand-alone modules) it will be very
>>>>> subject
>>>>> to:
>>>>>
>>>>> Error 29054:  Access can't add, rename, or delete the control(s) you
>>>>> requested.
>>>>>
>>>>> It's as if form corruption creeps in behind my back.  I can run the
>>>>> form
>>>>> repeatedly during development with no issues.  And then out of the blue
>>>>> the
>>>>> error crops up.  Sometimes re-deleting all of the controls is enough to
>>>>> correct it;  other times I have to pull a 'clean' form from back up in
>>>>> order to get un-stuck.
>>>>>
>>>>> Does anyone know what's behind this error?  Is there are way to keep
>>>>> his
>>>>> 'draw on load' code intact and keep this error from recurring?  Or do I
>>>>> need to re-create the form with hard-coded objects the way I wanted to
>>>>>
>>>> in
>>>
>>>> the first place?
>>>>>
>>>>> Thank you.
>>>>>
>>>>> Janet Erbach
>>>>>
>>>>>
>>>>>
>>>>>  --
>>>> AccessD mailing list
>>>> AccessD at databaseadvisors.com
>>>> http://databaseadvisors.com/mailman/listinfo/accessd
>>>> Website: http://www.databaseadvisors.com
>>>>
>>>>  --
>>> AccessD mailing list
>>> AccessD at databaseadvisors.com
>>> http://databaseadvisors.com/mailman/listinfo/accessd
>>> Website: http://www.databaseadvisors.com
>>>
>>>
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>