My company is currently evaluating a program that has been developed in Visual FoxPro (I think ver 8). During the demo of the software we noticed a couple of quirks. Upon asking the person to modify the software to eliminate these quirks, we were told that this is inherent with VFP and could not be eliminated or needed a lot of rework. I found this hard to believe and so started searching this forum to see it anyone else had the same issues. So here we go:
1. All numeric fields display a “,” (comma) for thousand delimiter during Edit and Display. When entering a value in the numeric field you must always enter the “.” (Decimal or full stop) to end the entry otherwise an extra zero is added to the numeric value. E.g. [1,00 .00] becomes [1,000.00]. We were told that the only way to ‘fix’ this would be to eliminate the ‘,’ thousand delimiter. I found it hard to believe that VFP does not allow numeric field to be formatted to displayed with ‘,’ thousand delimeter but when in editing mode it allows you enter the number without the thousand delimiter or save the data accurately. I found this entry in this forum but was not sure if it dealt with numeric fields.
2. In this application, the user opens a form and pulls up an existing record. Imagine the user changes some values in the fields of this form. If the user closes the form without hitting the save button, any edits made are lost. The application does not warn “Do you want to save the changes you have made” or something similar. Again, we were told that the only way to do this was to write code in every form that would take each field value and compare is against the database for that record to determine if it had changed – in other words a lot of extra coding. Again, I was surprised by that comment.
Are there any tips that I can pass on to this programmer regarding the above questions?
Many Thanks
1. All numeric fields display a “,” (comma) for thousand delimiter during Edit and Display. When entering a value in the numeric field you must always enter the “.” (Decimal or full stop) to end the entry otherwise an extra zero is added to the numeric value. E.g. [1,00 .00] becomes [1,000.00]. We were told that the only way to ‘fix’ this would be to eliminate the ‘,’ thousand delimiter. I found it hard to believe that VFP does not allow numeric field to be formatted to displayed with ‘,’ thousand delimeter but when in editing mode it allows you enter the number without the thousand delimiter or save the data accurately. I found this entry in this forum but was not sure if it dealt with numeric fields.
2. In this application, the user opens a form and pulls up an existing record. Imagine the user changes some values in the fields of this form. If the user closes the form without hitting the save button, any edits made are lost. The application does not warn “Do you want to save the changes you have made” or something similar. Again, we were told that the only way to do this was to write code in every form that would take each field value and compare is against the database for that record to determine if it had changed – in other words a lot of extra coding. Again, I was surprised by that comment.
Are there any tips that I can pass on to this programmer regarding the above questions?
Many Thanks