Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Error 1736 on new editbox
Message
De
16/03/2016 16:03:16
Lutz Scheffler
Lutz Scheffler Software Ingenieurbüro
Dresden, Allemagne
 
 
À
16/03/2016 11:32:37
Information générale
Forum:
Visual FoxPro
Catégorie:
Gestionnaire d'écran & Écrans
Versions des environnements
Visual FoxPro:
VFP 9 SP2
OS:
Windows 10
Database:
Visual FoxPro
Application:
Desktop
Divers
Thread ID:
01633174
Message ID:
01633191
Vues:
59
>Running into something weird. In an inherited application, I just changed a table to have a single memo field instead of two char fields for notes, and replaced the pair of textboxes on the relevant forms with an editbox. There are two forms involved. The first is pretty much display-only, shows a grid of all records on one page and detail of the currently selected record on a second. A button on that form instantiates a form class for editing the record.
>
>When I test here, all works as expected. Both forms open and show the right data. At the client site, the display form is fine, but instantiation of the editing form class fails with error 1736 and the message says "Error instantiating the object EDTNOTES." That's, of course, the newly added editbox that replaced the two character fields.
>
>I gave the client a separate EXE to make the database change and he ran it before testing the updated application. The fact that the first form opens correctly and shows the data correctly means the table was properly updated.
>
>I had the client send me the updated table and tested with it here and both forms work as expected.
>
>The only differences I can think of are:
>
>- the client is using Windows 10, while I'm on Windows 7 (but that he could send me the modified table means we're not dealing with virtualization);
>
>- the client has the data living on a mapped drive on a server, while I'm testing locally. Given that things are working generally, I don't see how this could matter.
>
>I'm at a loss. Any ideas?
>
>Tamar

Is the editbox of class edifbox or of some framework? I had sometimes the problem that I had open classlibxyz.vcx open while building the app (not compile all), but the classlib was open at my comp due to something else - and of completely unrelated folder.

This is I have a exe I use inside VFP that uses the same framework as the stuff I'm developing.

The exe uses XYZ.vcx (with internal path of the exes origin say c:\blabla\XYZ.vcx)

Now I alter a form in my IDE with a object based on c:\otherdir\XYZ.vcx. The form is opened fine - but sometimes the object is bound to c:\blabla\XYZ.vcx. instead of c:\blabla\XYZ.vcx after save.. This could be true for parentclass property as well. This all works fine as long as XYZ.vcx is somehow in SET("CLASSLIB"). Usualy on customers comp it tends to fail ...
Words are given to man to enable him to conceal his true feelings.
Charles Maurice de Talleyrand-Périgord

Weeks of programming can save you hours of planning.

Off

There is no place like [::1]
Précédent
Répondre
Fil
Voir

Click here to load this message in the networking platform