D
DRUAngell
I'm developing some basic web applications using Access as a backend. I'm
having an issue where my applications will not work any more after adding a
new field to a table in the existing database.
For example, I've got an application setup that displays customer
information from a table in Access onto the web page. It allows us to see
their information that they entered from a sample request form (we sell
hardwood flooring and offer free samples.)
So, they submit their request and the data gets inserted fine. We view the
info and ship out the samples and can then go back and see what has shipped
and what hasn't, what they got, etc. Sales people call them a week or 2
later if we haven't heard from them.
Today, they requested that I add a Notes section to the page they look at so
they can, obviously, add some notes after they make calls. I didn't have a
notes field in the database table, though.
So, I downloaded the database from my web server, opened it up in Access and
created the new field in the table. Then uploaded the database back to the
server and tried to run the application.
At this point, displaying data from the database still works perfectly fine,
however, adding new records or updating current records returns a "operation
must be an updatable query" error. In my searches on ASP forums for this
error it acts like it's a permissions thing...that I need to add the
ISUR_computername user to permissions and give it access. This is already
like that, though, and I double checked after re-uploading the new database.
What's strange is that it's still working locally on my test server here.
Just not on my actual web server. I am able to fix the problem by creating a
new database in Access and then simply copying/pasting structure+data from
the old database to the new one. When I upload that one and then add the
IUSR account everything works again.
What is happening when I add that new field that is stopping me from being
able to insert/update records?? Any informaiton would be greatly
appreciated. Thanks!
having an issue where my applications will not work any more after adding a
new field to a table in the existing database.
For example, I've got an application setup that displays customer
information from a table in Access onto the web page. It allows us to see
their information that they entered from a sample request form (we sell
hardwood flooring and offer free samples.)
So, they submit their request and the data gets inserted fine. We view the
info and ship out the samples and can then go back and see what has shipped
and what hasn't, what they got, etc. Sales people call them a week or 2
later if we haven't heard from them.
Today, they requested that I add a Notes section to the page they look at so
they can, obviously, add some notes after they make calls. I didn't have a
notes field in the database table, though.
So, I downloaded the database from my web server, opened it up in Access and
created the new field in the table. Then uploaded the database back to the
server and tried to run the application.
At this point, displaying data from the database still works perfectly fine,
however, adding new records or updating current records returns a "operation
must be an updatable query" error. In my searches on ASP forums for this
error it acts like it's a permissions thing...that I need to add the
ISUR_computername user to permissions and give it access. This is already
like that, though, and I double checked after re-uploading the new database.
What's strange is that it's still working locally on my test server here.
Just not on my actual web server. I am able to fix the problem by creating a
new database in Access and then simply copying/pasting structure+data from
the old database to the new one. When I upload that one and then add the
IUSR account everything works again.
What is happening when I add that new field that is stopping me from being
able to insert/update records?? Any informaiton would be greatly
appreciated. Thanks!