Andrew, >Ok nothing is jumping out at me, but if you do edit the data and the page >is reloaded or is it loading another page?
Yes, upon clicking the "Edit Employee" button the action attribute keeps you on this page. I'm open to it returning the user to the page from whence he came but I figured this way, IF it works correctly then the user can use the next screen (with the properly updated data) to confirm he indeed updated the record. >When you say the record is still the same, how is it still the same? In >other words do you load the edit page up to see the data has not changed, >or is it on the next page that the data has not changed? >On the next page are you pulling the data back out of the data base or how >are you relying on displaying the information again? >And one last thing, if you grab the ID of the record and look it up can you >vouch that the data has indeed been updated? As an example, when I first come to the page, I may have an employee with the name Peter Paulson. This name displays in the 'first' and 'last' fields and is pulled from the database correctly. I want to change the last name to 'Peterson' for example so I highlight/focus that field and change it from 'Paulson' to 'Peterson,' then click the "Edit Employee" button. On the client-side at this point, the page reloads but the datum is still 'Paulson,' on-screen...but if I pull up the database, I can tell the update statement has been commited properly because Peter's record in SQL now says 'Peterson' for the last name. Likewise, if I hit F5 on the client-side page that I'm currently on (emp_edit.cfm) it will ALSO show 'Peterson,' just not before I refresh, which is where I see end-users becoming confused. >You don't mention if there are any errors thrown, but I am assuming that >there isn't but is there anything in the logs that might help? The last entry in the application.log is "Variable UPDATEDONOR is undefined" but I'm pretty sure this was from when I entered <cfdump var="#updateDonor#"> on this page earlier and was because it is an update statement and not a 'normal' query...otherwise nothing in the logs. A perfect solution would be a one- or two-line bit of CF code that would essentially hit the refresh button FOR the end-user as soon as the update statement has been processed, or alternately, wipe the form fields clean as soon as processing is done, leaving the end-user with a blank form. Again, thanks for all your help, Andrew, and I look forward to your response. :) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-newbie/message.cfm/messageid:6037 Subscription: http://www.houseoffusion.com/groups/cf-newbie/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-newbie/unsubscribe.cfm
