Using Access for a web application data source has been challenging to say the least. Its security is unnecessarily confusing and is the cause of much frustration. The latest curse has been “Operation must use an updateable query.” You got to wonder who thinks up these meaningless messages. Perhaps it’s an ancient from the inquisition period.

The “Operation must use an updateable query.” message follows an attempt to update a table. A search of the internet found that many experience this problem and are as baffled as I on the cause. There are also many who offer solutions. I tried several with no success … until I stumbled onto Doug’s FAQs. Within seconds my problem was solved. All I did was grant USER full access to the directory containing my access mdb file. Thanks for the help Doug. I have added your site to my favorites list.

Don’t forget to include the connection object in the OleDbCommand, i.e.,
“OleDbCommand cmd = new OleDbCommand(“Select * FROM Node”,conn);” or you will receive the friendly error of “DataReader Error. Can’t Return Db Records” or and unfriendly error of “ExecuteReader: Connection property has not been initialized”.

Helen experienced this problem, solved it, and was nice enough to post the fix. Thanks Helen for your help.

Its something new every day. Today Response.Redirect won’t work. Now I have written this code more times then I am willing to count and it always worked. Example:

private void btMemberLogin_Click(object sender, System.EventArgs e)
{

Response.Redirect(“login.aspx);

}

What is wrong … well this code will not work if Page.Smartnavigation is true. Found this out from Dave who stated “… response.redirect() does not work if Page.Smartnavigation is true. Make it False the line prior to the redirect”.

The following code works.

private void btMemberLogin_Click(object sender, System.EventArgs e)
{

Page.Smartnavigation =true;
Response.Redirect(“login.aspx);

}

Sometimes it’s the simple things that are difficult. For example … while developing an ASP.NET web application it became necessary to catch the enter key and cause a page submit button click event to fire. There is code behind that must execute when the page is submitted. The enter key functionality just improves users experience. So how to implement …

After a couple of hours searching around and testing various options I found the following works perfectly. Just add to the page body tag and replace “btLogin” with your button name.

onkeydown=”if(event.keyCode == 13){document.getElementById(‘btLogin’).click();}”

The credit for this code snippet goes to the jsckol’s den.

Ray & Edee prepared a wonderful dinner to celebrate Mothers day. Ray grilled steak, and Edee prepared a really great salmon, baked potatoes and two great deserts. Looking back at this meal I sure could go for another serving. Afterwards Ryan & I played a game of Generals. Working together we destroyed the enemy.
This dinner picture was taken by Ray with his new Canon EOS 20D digital SLR camera. I now have a serious case of camera envy. The past few weeks I have been checking out various camera’s and settled on a Canon PowerShot A95. Now that I have seen the EOS 20D in action … don’t know if I can settle for the A95.

Just installed the latest version of MacJournal. This is a test to see how well it will post to my blog. Works great … easy connect and fast post.

.himg
{
float:left;
margin:10px;
}

Sold a 12-inch 1 GHz PowerBook on eBay. With the proceeds, purchased a new iMac G5, with a 17-inch screen, superdrive, wireless keyboard and mouse. Had planned on getting a Mac Mini. Just love its small footprint. However, with the desired upgrades it just made more sense to get the iMac. So far I am not disappointed with this decision.

Initial setup was a breeze. The mistake was using Apples system utility to migrate data from the PowerBook to the iMac. It successfully migrated everything. Unfortunately it configured the iMac to run like the PowerBook. All my efforts failed to correct the situation. Ended up rebuilding the system to return it back to its original condition. Following the reinstall, the system could not find bluetooth. Ended up contacting Apple via web chat. It was a great experience … they quickly provided the solution. That is “remove all USB connections, disconnect the power cord for one full minute, replace the power cord and start the system back up” the resultant startup recognized bluetooth and reconnected the keyboard and mouse. Like magic everything was working great.

Lesson learned … do not use the migration tool between a PowerBook and iMac.

This post is from MacJournal. The original purchased version would not post. However, upgrade v3.02 works. Now I can blog from MacJournal and save the content in my Journal. This could provide some additional security.