Hi folks
I have a problem with an order processing system built loosely on the Invoicing app supplied with A4. I am running A4v6.2 on a Win 98 PC. The data (dbf files etc) is kept on an NT server, which is mapped as drive F on the PC.
When I enter an order from a customer, I input the address, etc. then I tab to a region in the main form and enter the quantity, part number, colour option etc. That info is intended to be stored in Items.dbf. There is a logical field in each record in Items.dbf which has a default value of .F. (False). (This field is later used as a filter to process the data - after processing it is reset to True as a means of identifying which records have been processed)
So, in theory, the data is entered, the record saved, and the logical field is set to .F. by default.
Sounds ok, except that sometimes I am presented with an error screen when the record is saved, saying "Logical field entries are: T,t,F,f,Y,y,N,n, or ". If I then select the "continue" button I am thrown to the app's main menu screen and the record I was trying to enter is NOT actually saved.
This VERY often happens when I first enter an order. It sometimes (much less often) happens at other times, for example when I've entered maybe 10 orders or so. But it is much more common on the first order. Sometimes I can go for hours without the error, sometimes it is there every 10 minutes.
I only have one logical field in Items.dbf, so I am assuming that the error is associated with that field.
This problem is not a new one, but I have never got to the bottom of it. In all other respects the app works well.
Any ideas, anyone? Your opinions will be gratefully received.
Thank you.
Paul (UK)
I have a problem with an order processing system built loosely on the Invoicing app supplied with A4. I am running A4v6.2 on a Win 98 PC. The data (dbf files etc) is kept on an NT server, which is mapped as drive F on the PC.
When I enter an order from a customer, I input the address, etc. then I tab to a region in the main form and enter the quantity, part number, colour option etc. That info is intended to be stored in Items.dbf. There is a logical field in each record in Items.dbf which has a default value of .F. (False). (This field is later used as a filter to process the data - after processing it is reset to True as a means of identifying which records have been processed)
So, in theory, the data is entered, the record saved, and the logical field is set to .F. by default.
Sounds ok, except that sometimes I am presented with an error screen when the record is saved, saying "Logical field entries are: T,t,F,f,Y,y,N,n, or ". If I then select the "continue" button I am thrown to the app's main menu screen and the record I was trying to enter is NOT actually saved.
This VERY often happens when I first enter an order. It sometimes (much less often) happens at other times, for example when I've entered maybe 10 orders or so. But it is much more common on the first order. Sometimes I can go for hours without the error, sometimes it is there every 10 minutes.
I only have one logical field in Items.dbf, so I am assuming that the error is associated with that field.
This problem is not a new one, but I have never got to the bottom of it. In all other respects the app works well.
Any ideas, anyone? Your opinions will be gratefully received.
Thank you.
Paul (UK)
Comment