My first theory was wrong. It was not related to attempting to add a property 
at runtime that already existed. (And thanks Tracy :-). I do know that is the 
sort of thing that can cause C5 errors which is why I thought it was the 
culprit.) Although I do wonder why the statement at line 95 of the 
saveOriginalSize method is not contained in the IF statement immediately 
following. It looks like this:

.ADDPROPERTY( '_nOriginalWidth', .WIDTH )
IF PEMSTATUS( m.toControl, 'Height', 5 )
        .ADDPROPERTY( '_nOriginalHeight', .HEIGHT )
        .ADDPROPERTY( '_nOriginalLeft', .LEFT )
        .ADDPROPERTY( '_nOriginalTop', .TOP )
ENDIF

(Apologies for any stupid Outlook wrapping...)

It seems to me that if it is requiring height to be a property of the 
referenced object before adding the other 3, why isn't nOriginalWidth part of 
that bit?

Here's the answer to why it was blowing up.

In the form container, there is a pageframe. 
There are 3 pages in the pageframe. 
On the 2nd page there is a grid with 5 columns. 
The record source of the grid is set to a cursor. 
The control source of 3 of the 5 columns are compound expressions.
In 2 of those expressions, only field names were used (i.e. field1+field2, etc) 
as opposed to fully qualified names (i.e. cursor.field1+...).
I added the cursor name to at least one of the referenced fields in the 2 
control source expressions and it now works! Just like magic!
But I only had to add it to at least one field reference and I don't think it 
mattered if it was the first one.

Well I've got a few more things to work through but it feels more promising 
than it did earlier.

--
rk


-----Original Message-----
From: ProfoxTech [mailto:[email protected]] On Behalf Of Richard Kaye
Sent: Wednesday, March 06, 2013 12:51 PM
To: [email protected]
Subject: MWResize debugging fun

For anyone following along, I 've narrowed it down to the saveOriginalSize 
method where it attempts to add a property on the fly. My suspicion is the 
property is already there and attempting to add the same property causes the C5 
error. More to come...

--
rk


_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: 
http://leafe.com/archives/byMID/profox/DF1EEF11E586A64FB54A97F22A8BD0442188CB915D@ACKBWDDQH1.artfact.local
** All postings, unless explicitly stated otherwise, are the opinions of the 
author, and do not constitute legal or medical advice. This statement is added 
to the messages for those lawyers who are too stupid to see the obvious.

Reply via email to