SadOldGoth
Programmer
Hi Folks,
I've recently been experiencing a strange problem with an access 2000 app I've written. Everything will be working fine then someone else will try to start the app and be told it's corrupt, not recognised, all sorts of weird stuff. The only way to resolve it is for everyone else to log out of the program, and then for me to start and exit the program - everyone will then be able to access it.
As I said, weird, eh?
I've been banging my head on this one for a while - is it the speed of the machines, the memory, the fact we use citrix? All of these have been looked at, but as the problem is inconsistent it's been hard to track down. I still haven't as yet. After reading another thread I'm looking to update to SP-3 and see if that's of any use, but really I'm clutching at straws. Oh, and by the way, 15 or so other databases, written in a similar fashion, work quite happily and don't have this issue.
As I said, weird, eh?
Today, I've been updating the program and linked to my backend, ran the scripts to update the tables, got informed that I couldn't change the structure of linked tables, imported the tables, ran the scripts ro update the tables, imported them back in to the backend, went to delete them from the front end and then...without anyone using the database, without any access to the table, with a compact and repair done - I couldn't delete one table because another process was using it!
I quit the application and went back in and was able to delete the table quite happily.
Now, I don't know, call me suspicious (and long winded) if you like but there's something not right there, and also something that leads me to believe there is some link between the two issues.
Can anyone suggest what might cause this problem, because I'm losing my rag with this?
Thanks,
Jes
I've recently been experiencing a strange problem with an access 2000 app I've written. Everything will be working fine then someone else will try to start the app and be told it's corrupt, not recognised, all sorts of weird stuff. The only way to resolve it is for everyone else to log out of the program, and then for me to start and exit the program - everyone will then be able to access it.
As I said, weird, eh?
I've been banging my head on this one for a while - is it the speed of the machines, the memory, the fact we use citrix? All of these have been looked at, but as the problem is inconsistent it's been hard to track down. I still haven't as yet. After reading another thread I'm looking to update to SP-3 and see if that's of any use, but really I'm clutching at straws. Oh, and by the way, 15 or so other databases, written in a similar fashion, work quite happily and don't have this issue.
As I said, weird, eh?
Today, I've been updating the program and linked to my backend, ran the scripts to update the tables, got informed that I couldn't change the structure of linked tables, imported the tables, ran the scripts ro update the tables, imported them back in to the backend, went to delete them from the front end and then...without anyone using the database, without any access to the table, with a compact and repair done - I couldn't delete one table because another process was using it!
I quit the application and went back in and was able to delete the table quite happily.
Now, I don't know, call me suspicious (and long winded) if you like but there's something not right there, and also something that leads me to believe there is some link between the two issues.
Can anyone suggest what might cause this problem, because I'm losing my rag with this?
Thanks,
Jes
