If you are saying that your code from February now has the problem it means that the dbforms version or the environment must be at fault.
Using weekly builds to write production (i.e. for customer) code is not recommended by anyone. Customer code should be written using the latest stable release. If you end up with a bug that requires a hot fix, typically it patches the latest stable version AND you must test it thoroughly to make sure the patch didn't break anything else.
Try it with latest stable. I am using
dbforms_2.5_20050226.tgz
Bill
On Fri, 8 Apr 2005 23:25:07 +0200, Ivan Codarin <[EMAIL PROTECTED]> wrote:
Dear Bill,
thank you for your answer.
I add another information, the I will re.boot my system in my linux partition I
will re-do a checkout (if ppp will work) and a ant build.
Now I'm working with dbforms-sources directly on my project to debug.
The problem is the moment in which dbforms writes the first form. For example this is a HTML translation of a UpdateButton of "image type"
<input type="image" src="/sorgeco/layout/buttons/salva.png" name="ac_update_21_null_34"/>
for the table defined as:
<table name="tbl_provincia"> <field name="id_provincia" fieldType="varchar" isKey="true"/> <field name="provincia" fieldType="varchar" /> ....
The other times I click on the same button dbforms works correclty. I've just tested my 26 feb. jar... with no result.
Thanks
------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ DbForms Mailing List
http://www.wap-force.net/dbforms
