Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
VFP Switching Tables During a Report
Message
De
11/05/2000 10:37:42
Liam O'Hagan
O'Hagan Programming Ltd
Irlande
 
 
À
10/05/2000 21:21:54
Information générale
Forum:
Visual FoxPro
Catégorie:
Gestionnaire de rapports & Rapports
Divers
Thread ID:
00368247
Message ID:
00368553
Vues:
23
Hi David,

Thanks for your hint. You got it right on the nose.

I had a shortcut menu in the RightClick method of the textboxes on a grid of customers from which the user selected a report. This called a procedure which did the SELECTing the the REPORT FORM.

Following your reply I removed the shortcut menu from the grid and put the code in a button on the form. This fixed the problem.

Thanks to all for your input, especially Cindy Winegarden who must have the fastest reply in the UT - 3 mins after first post.


Regards,

Liam


>Hi Liam,
>I've had this same problem. It occurred when the print dialogue box went away reactivating the underlying screen which contained bound objects (expecially a grid!) Fox would then switch alias to redraw the object(s) wrecking the selected alias for the report.
>I can't remember exactly what I did, but basically you to prevent the forms activation during printing. eg using a custom print dialogue modal window.
>
>HTH
>
>>Hi all,
>>
>>I have an odd problem with the reporter that someone may have come across before. Any ideas very welcome...
>>
>>Situation
>>1) Numerous tables open...
>>2) SELECT blah blah blah into cursor CurRep
>>3) REPORT FORM blah blah blah
>>4) Report is fine until I move to the next page or zoom in or out then
>>I get an error message not found
>>
>> is one of a few variables in the report that is causing the error.
>>
>>After investigating (and much hair pulling) I discovered that VFP is SELECTing a table other than the result of the SQL statement (CurRep) DURING the report!
>>
>>Before the REPORT FORM command I inserted a messagebox(alias()) command to confirm that the correct table is, in fact, selected. A further messagebox(Alias()) command after REPORT FORM (and usual errors) will show that a completely different table is selected.
>>
>>Explicitly SELECTing the Cursor after the SQL statement makes no difference.
>>
>>During debugging I also discovered that if I issue a BROWSE before the REPORT FORM command, everything will go fine and the correct table will remain selected.
>>
>>Anyone seen anything like this before ??
>>
>>TIA
>>
>>Liam
Liam O'Hagan
MCP VFP Desktop Apps
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform