Friday, December 22, 2006

I am in Las Vegas to see the Vegas Bowl. BYU vs Oregon. The first quarter was ok. Neither team scored. Both made offensive errors. BYU dropped several easy passes, and Beck had some bad passes. After that it was all BYU. Oregon just didn't play well tonight. They finally scored in the 4th quarter on a long TD pass. They really didn't do anything all night.

The highlight was at the beginning when volunteers from Nellis Air Force base rolled out a football field size American Flag. Then the during the National Anthem, 2 air force jets flew over and hit the afterburners right above us. COOL! Definately the highlight of the evening. I want to take my boys next year so they can experience this.

Wednesday, December 13, 2006

My users have been requesting a seemingly simple feature for a while now and I could not get it to work.
 
When they enter a value, they are prompted with a javascript confirm (Ok/Cancel) box if the value is over $1,000,000.  If the choose "OK", no problem.  But when they choose cancel, they wanted to be put back in that same field.  I should just be able to do the following:
 

function checkValue(){

if (document.getElementById('valuation ').value >= 1000000){

if (confirm("This value is over $1,000,000. Are you sure you meant to enter such a large value?")){

}

else {

document.getElementById('valuation').focus();

}

return false;

}

}

I was able to set focus to any field, except the one I just came from.  The only hack I was able to find was to set focus first to another field, then the field I came from and then use the follwing in my <input> statement.  

onFocus="this.select()"

Here is the javascript function I had to use:

function checkValuation(){

if (document.getElementById('valuation').value >= 1000000){

if (confirm("This value is over $1,000,000. Are you sure you meant to enter such a large value?")){

}

else {

document.getElementById('otherfield').focus();

document.getElementById('valuation').focus();

}

return false;

}

}

 
-------------------------------
David Mineer

Tuesday, December 12, 2006

I just found out that I can have the contacts on my cell phone backed up automatically. Not only that, it provides a web interface for adding, updating and deleting the contacts on my phone. I have a verizon phone and you can find out about it at:

http://www.verizonwireless.com/backupassistant

It does const $1.99 a month. But as often as I drop phones in a glass of milk, it is worth it to me.

Several of my users have been complaining that iGoldmine was not working for them. I am not sure when it quit because iGoldmine sometimes doesn't get used for weeks at a time. But I was pretty sure it was working until sometime in November maybe even towards the end of November.

Anyway, I started researching this and came to find out that I could not run the goldmine executable which is on a network share, from the machine running my iGoldmine server. The iGoldmine server is W2K 2003 server and is just a member server of my domain. The error I was getting when trying to run the goldmine executable was:

"windows cannot access the specified device, path, or file. You may not have the appropriate permissions to access the item."

I decided to try and run some other .exe files on different network drives and sure enough, same error on all of them.

Goldmine tech support is usually awesome, but this time they just pooped out on me and had me so mad I had to go get a Dr Pepper to settle down. They didn't want to help at all.

Turns out the issue was with the Internet Explorer Enhanced Security Configuration. You can get to this in Control Panel-Add/Remove Programs/Windows Components/. After that you can check or uncheck the two options: "For administrator Groups" and "For all other user groups". Both were checked, so I unchecked them and then I was able to access files over the network.

I didn't have the same problem logged in as myself. I was able to run those files, other users, however could not and hence the problem. There must have been a windows update that changed the IE config and hence caused this problem. I would have thought the Goldmine folks would have encountered this already, cause it has probably been a month or so.