Lately we've noticed that, when using the Invoice form of our application, there is a noticeable delay when clicking from one tab to the next, sometimes taking as long as 4 or 5 seconds.  I back up the application at the end of every month, and have found that this occurs starting at the end of December.  The backup copies are saved on my local hard drive, so I know it's not a network problem (it occurs wherever the file is saved.)  I also save a copy of the DSR every time I make a change, as well as copies of the application before and after the reconciliation.

After firing up all the application backups made since November, I've found that the problem occurs in my "2011-12-21 after reconciliation MIARA" application, but not in my "2011-12-21 before reconciliation MIARA" application.   So something in my "2011-12-21 reconciliation MIARA" DSR is the culprit.

Any advice on what would be the best way to track this down?    I'm not sure if it's a programming change or a design change, or maybe both.  My plan right now is to use Designer to create a DSR for each of the apps, and then try to compare them.  Is there a way to export the programming for the entire app into a text file, of do I need to do it form by form?  Comparing text files is easy, I use a program called Beyond Compare.   Comparing the DSR files themselves is not helpful with this, since all I see is computer code in the comparison window.

Thanks in advance for your help.

Thanks Ray, I'll try all of your suggestions.   What I've found so far is that prior to the reconciliation my Invoice form's first tab looked like this:
http://www.jamiara.com/images/Invoice-2011-12-21-before.jpg   
and afterwards it looked like this:
http://www.jamiara.com/images/Invoice-2011-12-21-after.jpg

As you can see I enlarged the "Lookup" field (called "Checkcode" in my programming) and moved it above the "Code" field (called "Bill_to_code" in the programming), with everything else on the tab shifting down a bit to accommodate.  The size of the display type for this field was increased as well.    My boss refuses to buy glasses.   

Comparison of the exported programming for the form shows no change to the code except that the following moved from line 1723 in the printout to line 1840:

** PROGRAMMING SECTION: [Bill_To_Code] [On Element Change] **
// Populates the Customer info section

IF (@ISBLANK(Bill_To_Code) or Bill_To_Code = 0)
THEN
{
	ClearCustInfo()
}

ELSE IF NOT @IsBlank(Bill_To_Code)
Then
{
	LookupBillToInfo()
}

// Recalculates the Customer Discount amount if the Percentage is populated by the Workorder

IF (Details_Customer_Discount_label = "CUSTOMER DISCOUNT" AND Details_Customer_Discount_Percentage > 0)
THEN CalculateCustomerDiscount()
 

Such relocation would be expected when fields move around, I presume.

I'm going to try your suggestions, thanks again, but perhaps the solution is as simple as putting things back where they were.

After trying the above suggestions with no success, I was sad.      So I took a break, had a walk away from my office, sipping a mango flavored Gazzu.

Then I redesigned the Code and Lookup fields, setting them to the same box size and font size, placing them on the same Y coordinate and putting them back in their original order in the flow.  The problem....went away.

Now I am happy and full of pep, yay.   

Curious as to what may have been happening though.  Any ideas?

Slightly off topic - I've noticed before that if I inadvertently save my program designer with 'snap to grid' ON in the Editing Controls command window, screens are sluggish.  Once I go back in and turn that switch to OFF, everything's good again.

Ray,

I can't clearly remember if the sluggishness occurs while I'm still in Designer, or if it carries over to runtime.

I actually have a vague recollection of someone mentioning that awhile back (a year?  more?) and Mark commented that he had fixed it (but I can't remember for which version - past or future pending).

Hello Scott,

Yeah I saw it on the links you had posted just wasn't sure if anyone had a smaller monitor. I'm not sure what might have been the cause of it then.

-Ray