Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Early binding?
Message
Information générale
Forum:
Visual FoxPro
Catégorie:
Classes - VCX
Titre:
Divers
Thread ID:
00395657
Message ID:
00395710
Vues:
14
>Another option would be to use only one grid and set its properties at run time (kind of late binding) based on the mode the form is running. Your idea of creating 2 separate classes sounds more elegant, though.

Thanks. I've just finished the implementation of this idea. It works!!!!

>
>>>Hi everyone,
>>>
>>>I have this problem: I have a form with 2 grids on it. This form could be run with different parameters (which evalute in Form.Load) and then I remove one Grid and use only the one, which is relevant, e.g. for ParcelProcessing I remove Transaction grid and leave Parcel grid and vs. Both grids are completely designed, e.g. all columns have controlsource, which is set in design time (in Property sheet).
>>>Now my problem is: I use different tables depending on parameters. Parcel Processing may not have fields, which are relevant for Transaction Processing. I'm getting an Error: 'grdBldMstr or one of its component: variable Mortgage is not found' when I try to run this form for Parcel Processing. I tried return .f. from Init of these grids, but it doesn't help. How can I solve this problem?
>>>
>>>Thanks in advance.
>>
>> As a solution of this problem I may think about saving both grids as class and then instead of removing grid add the necessary grid. So now my question is:
>>how can I save an existing object on a form as a class?
>>
>> Thanks in advance.
If it's not broken, fix it until it is.


My Blog
Précédent
Répondre
Fil
Voir

Click here to load this message in the networking platform