Check your 3G iPhone for cracks

Unclear if it's just the white ones or all of them, but the new phones are cracking:

Cracks 'appearing' in new iPhone 3Gs - The Unofficial Apple Weblog (TUAW)

...The problem is not the plastic, but that the metal frame is too small for the plastic to lock on without causing the stress fractures.' It's pretty clear Apple has a manufacturing defect on its hands.

For those with cracks, taking it back to the Apple Store (or possibly the mobile phone retailer where you made your original purchase) is your only recourse. Several people have noted here and elsewhere that they've successfully had their handset replaced after a careful inspection....

As an Apple customer, I'm used to this. My MacBook plastic cracked, my iMac display partially delaminated, etc.

I have a 3G iPhone so I'll watch for the cracks. Might be important to get their existence documented early to be in line for a recall solution.

I'm not sure what the value of a phone swap is, if it's a real manufacturing defect the new one will have the same problem.

Google Mobile and local search

I sometimes complain about the use of video in place of written description, but this screencase is superb: Use Google Mobile for the iPhone for Quick Local Lookups.

There's a link to an earlier Google Mobile review that describes the service in more detail.

Superb stuff. Now if Google Mobile would only allow me to switch between my gmail and Google App personae ...

My iPhone is pretty much a gPhone at the moment -- I use Gmail IMAP with iPhone mail.app, Google Maps, and Google Mobile (fantastic). I'm very much hoping Google will introduce a gCal solution for the iPhone -- the current calendar view is a limited read-only list of appointments. I've just about given up on MobileMe.

Microsoft Access 2007 reliability issues and suggested workarounds

The following TechRepublic list was written for Access 2007. My impression is that Access 2003 is becoming less reliable over time, probably due to security fixes that aren’t fully tested on 2003. Even so, I think 2007 may have more corruption problems, though presumably Microsoft will eventually fix them.

10 ways to prevent Access database corruption | 10 Things | TechRepublic.com

#1: Split your database …

#3: Don’t use memo fields

Avoid using memo fields if possible. They often, indirectly, cause corruption….  If you need memo fields, keep them in separate tables and create a one-to-one relationship to the parent table(s). Even better, move memo tables to a separate backend database file and name the file accordingly, to indicate its purpose.

#4: Don’t store picture files

Usually, you shouldn’t store picture files in a database. If you must, treat them the same way you would a memo field (see #3)…

#5: Create temporary tables to speed up queries

If you run complex or nested queries (where one query pulls data from others that hit still others), Access may write a lot of temporary data that you never see. Most often, this happens when a query that works with a small amount of data performs slowly, putting stress on the JET engine. If Access chokes during this process, you can end up with a corrupt backend file.

To prevent this problem, write some of the temporary data to temporary tables. There’s no universal method to recommend. Analyze the specifics and run some tests to find the best solution. However, sometimes the use of just one temporary table can minimize the chance of corruption and speed up the queries by a factor of 10 or more.

#6: Be careful with wireless networks (WiFi) (and other less reliable network connections)

Access 2003 does not support views, I think they would help with #5.

The list of “risky” behaviors is an indictment of Microsoft’s software quality. Memo fields, for example, are very useful! I never used to see problems with nested queries in 2003, but I have recently.

My personal favorite is #1 on the list. I store data that isn’t going to be changed in a read-only file (set read-only file attribute).

My Palm to iPhone migration challenge -- summarized

Google Docs - Palm migration is a spreadsheet that captures in a glance how very hard the Palm to iPhone migration is. There's a feed for change notification.

I'm omitted Palm apps that are readily replaced. Obviously the media, communication and entertainment capabilities of an iPhone spank the Palm.

On the other hand, those capabilities are not nearly as essential to me as the core "PDA"/"PIM" (personal digital assistant, personal information management) capabilities of the original PalmPilot -- and the database I use to extend those capabilities.

Of the 10 core functions I have identified migration strategies for exactly 3 of them.

Suggestions are most welcome, but I need suggestions that allow me to migrate my data as needed. Data lock is not acceptable for this material.

PS. I now wonder if some of the missing functionality is tied up in software patent issues.

Update 8/3/08: Why the Palm Centro may incent Apple to address Palm to iPhone conversion.

A missing iPhone app: Passcode lock now!

I'd gladly pay a dollar for a "Passcode Lock now!" iphone App.

The iPhone provides Passcode auto-lock. That's fine, but it's dangerous to enter a passcode while driving. So I set the interval pretty long -- to about an hour.

An hour is fairly long. I'd like the option to passcode lock the iPhone on demand. Tapping on an app would be just the thing.

Of course I've no idea whether the API allows software activation of the Passcode lock. I can imagine that might be abused ...

Google adds iCal support

Yesterday I wrote about BusyCal and Spanning Sync for iCal to gCal sync.

Today Google introduced its own version of iCal to gCal sync ..

CalDAV support comes to Google Calendar - The Unofficial Apple Weblog (TUAW)

... Google has just quietly introduced CalDAV support to Google Calendar. CalDAV is the protocol that iCal uses to transmit data over the web. Although some other mail and calendar programs support CalDAV, right now Google Calendar is only compatible with iCal...

After following Google's detailed instructions, you can add your Google calendar account to iCal. Any changes you make in iCal will be transferred over to Google and appear in Google Calendar within about 15 minutes. Likewise, any changes made in gCal will be updated...

Based on Google's Outlook sync tool train wreck I wouldn't jump for joy just yet. I'll certainly take a look, but for once I'm going to resist and watch for the screaming over the next week. I've done my early adopter duties for this month!

For one thing, I'd like to figure out how to match specific calendars. I think that looks doable with some tweaks to the standard instructions ...

iPhone crashiness - try reset nightly

I had my first iPhone crash today -- while switching to Apple's iTunes Remote app.

I've been playing with several apps, so I'm not that perturbed -- yet.

I'm now going to try rebooting it each time I put it in the night-time charger:

Apple - Support - iPhone - Phone Troubleshooting

To reset iPhone, press and hold the Sleep/Wake button and the Home button at the same time for at least 10 seconds. During this time, a red 'power off' slider may appear and the screen may go black, but do not release Sleep/Wake and Home buttons until the Apple logo appears.

Should clear out some gremlins. It's an old Windows trick.

Incidentally, here's how to kill an app (If I have to do this, I'll reset at the next convenient time):

Try pressing and holding the Home button for at least 6 seconds to close a frozen application. Then restart (power cycle) by press and holding the sleep/wake button until the red slider appears ...