When iBank goes bad

Some time back I made the conversion to iBank for keeping track of our finances. Then last year an update to iBank 4 came out. I grabbed it and started the update. For a blissful 30 seconds it all looked good and then came the dreaded error message.

The operation couldn’t be completed. The backslash is a wildcard char, and cannot appear unescaped at the end of a string.

So starting last October a number of posts were exchanged on the support forums. It ended not so well with this post. Asked to once again supply the data that had taken a fair bit of time to prepare the first time around. I was tired of the dance and just walked away. How hard can this be I wondered? Being a database guy it seemed pretty obvious that this was a problem with a '\' being at the end of a string and not being escaped.

Subscribe to navicat