Hello everybody,
Here's the story. We have a database which functions as CMDB and Helpdesk tool with two main forms, a helpdesk form which registers calls and a hardware form which contains details of all hardware items also with which users own it and from which department they are. This has worked correct for a long time. There is a front- and a back end.
There is at the moment, however, a big issue. When you enter new data everything is ok, but when you want to change the data a very strange problem occurs sometimes (quite often).
Both forms have the problem that quite often when you are in an existing record and make a selection from a combobox it writes the mutation to the preceding record!!! First, this problem only was present in the hardware form. Now it is also occuring in the helpdesk form. So in the helpdesk when you change the status of a call to solved it might be that it closes the preceding call. Or when you change the IT employee that has to deal with the call it changes it for the preceding record and leaves the current record unchanged. Also in case of a hardware item when you register it on a user it writes the name to the preceding hardware item, making you also lose the data from that record. This totally messes up the database. When you then close the database and start it up again it works correctly for some time, only later it starts malfunctioning again.
For years it has worked correctly. I think the issue does not arise from the code, but from something else, but I'm not sure what.
I have tried the following:
Import the databases into a two new databases (front-end and back-end). Delete all relationships and indexes of the 2 main tables. Create new tables with only the structure. Write the data to the new tables with an append query. Recreate the indexes and the relationships and delete the old tables. It appeared to solve the problem, but it has returned.
Can anybody please give me some advice. Any help would be appreciated.
Here's the story. We have a database which functions as CMDB and Helpdesk tool with two main forms, a helpdesk form which registers calls and a hardware form which contains details of all hardware items also with which users own it and from which department they are. This has worked correct for a long time. There is a front- and a back end.
There is at the moment, however, a big issue. When you enter new data everything is ok, but when you want to change the data a very strange problem occurs sometimes (quite often).
Both forms have the problem that quite often when you are in an existing record and make a selection from a combobox it writes the mutation to the preceding record!!! First, this problem only was present in the hardware form. Now it is also occuring in the helpdesk form. So in the helpdesk when you change the status of a call to solved it might be that it closes the preceding call. Or when you change the IT employee that has to deal with the call it changes it for the preceding record and leaves the current record unchanged. Also in case of a hardware item when you register it on a user it writes the name to the preceding hardware item, making you also lose the data from that record. This totally messes up the database. When you then close the database and start it up again it works correctly for some time, only later it starts malfunctioning again.
For years it has worked correctly. I think the issue does not arise from the code, but from something else, but I'm not sure what.
I have tried the following:
Import the databases into a two new databases (front-end and back-end). Delete all relationships and indexes of the 2 main tables. Create new tables with only the structure. Write the data to the new tables with an append query. Recreate the indexes and the relationships and delete the old tables. It appeared to solve the problem, but it has returned.
Can anybody please give me some advice. Any help would be appreciated.
