asked
Access Database Issue - writing over a location in database
Hi Everyone! The company I work for has a Access database which a HR web form links to for updating Employee data. When an employee is updated and the form is submitted, the database is locked on a specified row location. For ex.) If I modify my Employee record, the form is making the change to a StaffID of 1743. Originally it was updating my account on StaffID 1742. For testing purposes I removed the StaffID #1742 and that is when the number went to #1743. I know we should not use Access for web and we are in the works of migrating to SQL but for now the HR page is looking at Access. The total rows returned when queried is 530. I have never seen this happen before. The Inserting of new employees works fine but it is when we modify that there is an issue. I have expressed to the web developer that his code could be picking up an incorrect ID and not the one that the person is logged in as. But he has pushed back on this and says the database is corrupt. I have created a new database with the exact data and still the same issue happens. Has anyone seen any issues with Access database maybe getting "stuck" on one row line? If so, how can this be resolved? Any info would be great! :)
I have not done much with Acess in a long time. I believe though with Access if the database were corrupt the complete file itself would be corrupt.
If you can show that when you logon to the web form and it is picking you up as StaffID 1743 when your ID should be 1742 (or something else), I don't see how the developer could argue with you. He needs to prove or provide information (captured errors, etc) that lead him to beleive the database is corrupt.
I don't really understand the "getting stuck" comment. From what you already stated if you logon to modify your HR record and it is returning a single record, although the wrong one, I would not say it is getting stuck. The code is wrong in matching your login to the staff ID record.
Getting a developer to admit his code is wrong can be a big task so I would approach him/her carefully. Maybe start out saying in trying to figure out what is wrong with the database file have them show you how their code matches the login to the Staff ID.
If you can show that when you logon to the web form and it is picking you up as StaffID 1743 when your ID should be 1742 (or something else), I don't see how the developer could argue with you. He needs to prove or provide information (captured errors, etc) that lead him to beleive the database is corrupt.
I don't really understand the "getting stuck" comment. From what you already stated if you logon to modify your HR record and it is returning a single record, although the wrong one, I would not say it is getting stuck. The code is wrong in matching your login to the staff ID record.
Getting a developer to admit his code is wrong can be a big task so I would approach him/her carefully. Maybe start out saying in trying to figure out what is wrong with the database file have them show you how their code matches the login to the Staff ID.
Thank you very much for your feedback. After speaking with my Manager and the Web Programmer as of last Friday they both pushed back and wasted a day on DB corruption theory. Website was down since Friday and this AM they found as I had expected - web page had "bad" code/corrupt. As far as getting stuck goes, bad terminology, the record was always referring back to row #367 when making changes. :)
You may work with Access database thanks to following software
Access Fix Toolbox program opens, reads, exports, recovers access database.
It must be access database corrupted, make use [
http://www.access.repairtoolbox.com][1] software supports ms access databases starting with MS Access 97 version program [1]:
http://www.access.repairtoolbox.com
2 People are following this question.
