This is a multi user Paradox 9 application which has been running sucessfully for a number of years, and untouched for the last 4 or 5 years.
There are now a number of 'strange' things occuring on different machines running the same code. I will detail each below.
1. A form has a calculated field - counting a field. Since creation it has counted those records in the sourrce table which contain a value in the field. One machine on the network has recently been rebuilt, and this machine is now counting all records in the source table.
2. There is a query immbedded in a piece of code. It receives a date range from the user. Until 23 April it ran on all machines in the network. Now it will only run on a single machine. We cannot think of any changes that took place on any machine or the network at this time. It is related to the machine, not the user. I have trapped the code and found that it fails on the exeute statement, and there is no error message - it just hangs. On the machines that fail, the query will run successfully if it is started as a Query rather than within code. One of the tables that make up this query is not a paradox table - it is a foxpro table used by an accounting system.
3. I noticed that the machine that works runs the query with a date of dd/mm/yyyy - which is correct for us. One of the machines that fails will run this query with a date of mm/dd/yyyy - this is just a side issue and is not the reason for the query failing in code - as I was testing with a date that would be valid with either format.
I guess there is something machine specific that lives locally on the pc - but after hours of investigation by myself and the network techie, we can find nothing.
Any thoughts greatly appreciated.
There are now a number of 'strange' things occuring on different machines running the same code. I will detail each below.
1. A form has a calculated field - counting a field. Since creation it has counted those records in the sourrce table which contain a value in the field. One machine on the network has recently been rebuilt, and this machine is now counting all records in the source table.
2. There is a query immbedded in a piece of code. It receives a date range from the user. Until 23 April it ran on all machines in the network. Now it will only run on a single machine. We cannot think of any changes that took place on any machine or the network at this time. It is related to the machine, not the user. I have trapped the code and found that it fails on the exeute statement, and there is no error message - it just hangs. On the machines that fail, the query will run successfully if it is started as a Query rather than within code. One of the tables that make up this query is not a paradox table - it is a foxpro table used by an accounting system.
3. I noticed that the machine that works runs the query with a date of dd/mm/yyyy - which is correct for us. One of the machines that fails will run this query with a date of mm/dd/yyyy - this is just a side issue and is not the reason for the query failing in code - as I was testing with a date that would be valid with either format.
I guess there is something machine specific that lives locally on the pc - but after hours of investigation by myself and the network techie, we can find nothing.
Any thoughts greatly appreciated.