Living with Access 2007: "Disabled Mode", Trust Center, and a Bug

I have to live with Access 2007 at work. It's a mixed bag. Some things from Access 2003 have been improved. On the other hand, I despise the ribbon bar. Other things have not been touched: Access tables links still use path names (argghhhh), links still break when paths change, scripted column values pass the script rather than the script result (produces very bad side-effects), you still can't link in a query so that you could use the query results, there are no "view" equivalents, etc, etc.

Some things are really nasty. Here's one from an unanswered question on an Access site:

Re: Query Access 2007 "Disbled Mode"

... When I run the Make Table Query it says in the lower left corner the following error:

"The action or event has been blocked by Disabled Mode".

Access 2003 and 2007 alike have this idiotic question you have to answer on startup -- something about enabling "risky" stuff. I can't figure out how to disable the question. I think it's related to this problem. In my case I needed to write the output of a script from an Access 2003 formatted file to a new Access 2007 formatted file.

So how does one fix this? A member of the borg tells one how to discover disabled mode status programmatically, but that's no help. This probably helps:

http://blogs.msdn.com/access/archive/2005/11/01/488022.aspx

... Disabled mode and the Office Trust Center are designed to make it easier for a user to make trust decisions in scenarios where scripts that launch Access do not come into play.

There are scenarios, where developers of a solution want to ensure that code in Access (startup form/ macro or otherwise) always executes. In such cases the recommended approach is to ensure that one or more of the following conditions are met:

• The database is signed with a trusted certificate.
• The database is installed in a trusted location.

By meeting these conditions, the code within the solution will always be enabled. In scenarios where neither of these conditions can be guaranteed, Access can be made to revert to its legacy behavior of a modal startup trust prompt, that will launch and execute code in the database or not open the file at all. To revert to this legacy behavior set the following registry key:

HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Access\Security\

Value: ModalTrustDecisionOnly = 1 (DWORD)

Okay, let's look into the trusted location:

Click the Microsoft Office Button , and then click Access Options...

Click Trust Center, click Trust Center Settings, and then click Trusted Locations.

...If you want to create a trusted location that is not local to your computer, select the Allow trusted locations on my network (not recommended) check box.

Click Add new location.

 ... We recommended that you don't make your entire Documents or My Documents folder a trusted location. Doing so creates a larger target for a hacker to potentially exploit and increases your security risk. Create a subfolder within Documents or My Documents, and make only that folder a trusted location.

In the Path box, type the name of the folder that you want to use as a trusted location, or click Browse to locate the folder.

If you want to include subfolders as trusted locations, select the Subfolders of this location are also trusted check box...

So I did this and got the error message: "the path you have entered is not a valid location or cannot be used ...". I think I'm getting this because I use drive letter substitution to get around the age-old access problem of linked file path dependencies.

A Google search on the last suggests the same problem arises with network drives, despite the claim that Access will allow trusted access to network drives. So this is probably a bug.

So I gave up, changed my trust center settings to "show the message bar", exited Access 2007, changed the default file mode to Access 2002-2003, restarted, clicked "enable everything" and I was able to run the query.

TSclientX: replace Microsoft's Remote Desktop Client with one made for OS X

I use Microsoft's Remote Desktop Client to control XP machines at home and work and to connect to Windows Terminal Servers (Win 2003). The terminal services interactions in particular are awesome, there's nothing comparable in the OS X world. It's my top complaint about OS X -- that Apple has never even tried to match Microsoft's six-plus year old remote control technology. 

Microsoft's Remote Desktop Client works very, very well under XP. They even made a client for OS X, but they stopped updating it a while ago. It's increasingly flaky, though I use it with some success even under 10.4.10 on a MacTel. I doubt, however, that it will work at all under 10.5 (BTW, I don't expect 10.5 until the spring of 2008 -- projects that big don't slip by only a few months, if it ships in October 2007 it will be dangerous).

So I'm very interested in TSclientX - An alternative RDP Client for Mac OS X. Runs native on Intel. Alas, it requires X11 ..

TSclientX is a Windows Terminal Services client for Mac OS X.  It appears to be a regular Mac OS application but is in fact an assembly of free software working in concert to provide similar (better?)  functionality to the official Remote Desktop Connection from Microsoft. Additionally, there is a nice tidy VNC Viewer built right in as well.

What makes TSclientX interesting compared to other Mac RDP Clients?

- SeamlessRDP is brought to you by Cendio's SeamlessRDP component.   It was originally introduced in rdesktop 1.5 and just simply rocks...

- Stability and speed on Intel Macs (and PowerPC Macs for that matter)   has been found by many to be superior compared to the official  Mac RDP client.

The most interesting ingredients are:

rdesktop 1.5 - http://www.rdesktop.org
An open source client for Windows NT Terminal Server and Windows 2000/2003 Terminal Services

tsclient 0.148  - http://www.gnomepro.com/tsclient A frontend for rdesktop and other remote desktop tools

VNC Viewer 4.1.2 - http://realvnc.com Virtual Network Computing

libao 0.86 - http://www.xiph.org/ao A cross platform audio library with CoreAudio support.

The GUI uses an optimized GTK+ build, specifically compiled for TSclientX.  Like most Unix-derived software on the Mac, Apple's X11 is required...

Skim for OS X: From Klein to DeLong to me

Ezra Klein likes Skim. I can see why. I downloaded and installed the compact open source application, and even at version 0.51 it's sweet.

I'm an Acrobat guru -- but I'm not a fan. Adobe is not a great software house on XP, and they're truly weak on OS X. They ignore basic OS rules (such as not running as an admin user) and their application update process is profoundly broken. Let's not talk about their browser integration ...

So I know Acrobat Pro extremely well, including the esoteric bits, but I've avoided both the Pro app and the Reader on OS X. I use Preview, a suprisingly powerful application that's a bit short of PDF oomph. Skim adds real notes (not the weird image overlays Preview sort-of provides) and some nice PDF browsing capabilities -- and we're only at 0.51.

Skim looks very promising.

Blogger: Replacement for BlogThis!

I've had quite bad luck lately with the Blooger BlogThis! bookmarklet. It simply fails to open much of the time with both Firefox and Camino. On the other hand the Google toolbar for Firefox "Send To Blogger" function has been working quite well, and of course on the XP platform there's Microsoft's unrivalled "Live Writer" for both IE and Firefox.

Alas, Camino and Safari are left out in the cold, though the BlogThis! bookmarklet seems to work best when I try it with Camino.

Send To Blogger is no panacea though. There's still no category/tag support.

LiOn battery care: it's the heat

Apple has a page up on maximizing iPhone battery life. Some of its universally applicable to all portable devices, others apply to all iPods (see also). The list below includes the web site info, and some of my own superstitions. The item new to me is bolded ...

• Heat. LiOn batteries are damaged by heat. (I don't know if extreme cold damages the battery or simply transiently reduces output.) Keep your iPod, iPhone or laptop cool, especially when charging. Temps over 95C will reduce lifespan, so avoid leaving it in car in the summer. (A LiOn battery that's very hot during charging may be malfunctioning, as in pre-explosive. Don't wait for it combust, get it replaced.)
  
• Use the battery at least monthly. LiOn batteries don't like storage, they age even if they are never used, though this effect is less severe than it once was. If you buy a device that's been on-the-shelf for a year you should expect inferior battery performance.
  
• Run the charge from 100% to about 15-20% and recharge. (I've read this elsewhere and it gets periodically repeated. Others say there's no real problem with frequent "top off" charges except that the "battery life prediction" becomes less accurate.) A full discharge every 1-2 months will make the battery indicator more accurate. LiOn batteries age faster if they're totally drained repeatedly.
  
• Turn off bluetooth, 802.11, etc unless you need it.
• EQ settings: "Adding EQs to playback uses more of your processor, since they aren’t encoded in the song. Turn EQ off if you don’t use it. If, however, you’ve added EQ to tracks in iTunes, you’ll need to set EQ to “flat” in order to have the effect of “off,” because iPhone keeps your iTunes settings intact. Go to Settings > iPod > EQ."
  

Google Apps: An evidence-based impression

I've done enough with Google Apps, including some tech blog and notes comments, that I can provide some experienced, nay, bloodied, opinions. A short opinion, because I need to get to sleep.

1. Google Apps are vastly easier to work with if you get your domain and application set through Google (eNom) rather than trying to convert an existing site.
2. You can create and share a document, but that doesn't mean anyone else in your domain can see it. You have to send an email for them to open it, I think then it stays in their document list.
   
3. The services are very loosely "integrated". There's not even a common "start page" link. You move from service to service. Blogger is sort of integrated through the esoteric and obscure "blogger custom domain" feature -- but Blogger doesn't show up in the service list. There's no maps integration.
4. Google's Page Creator and file sharing functions are abysmal. The Page Creator is buggy.
   
5. If you want someone to be able to edit a web page they need to be a full administrator. There are only three privilege levels: administrator, user and outsider.
6. The Calendaring integration is clumsy. You can add a "Calendar" to the "start" page, but it's only a user's calendar. You can't add the shared organizational calendar or any other calendar to the start page. Calendar discovery is obscure.
   
7. Speaking of widgets, there's an lot of junk in the widget collections Google offers. Google doesn't tell us which are written by their people, and which are marketing efforts.
8. There are are bugs everywhere. Did I mention bugs? Also lots of missing functionality.

On the upside, it's free and the deal for non-profits is particularly good. On the downside it's very raw.

Aperture launchus interruptus due to Shuffle dismountus interruptus?

Most of the many bugs I run into with OS X involve the combination of managed users (less than standard user privileges), fast user switching, and devices "owned" by a single user (try switching users while an iPod is associated with a user).

I wonder if this bug falls into that category. I'd updated QuickTime and iTunes and restarted. Everything seemed well, but Aperture wouldn't launch fully. It displayed the splash screen and hung -- as though it was waiting for something. No SPOD, no spinning wheel, nothing.

I tried a few times and decided to restart. My iMac then hung on shut down, with the "spinning radial lines" effect. I left to do a few things, and 20 minutes later it was still "spining". Then I noticed the iPod shuffle light was blinking yellow. I pulled the shuffle from its cradle and the system shut down immediately. On reboot, with the Shuffle removed, Aperture opened normally.

Presumably on startup Aperture is polling disks, and the Shuffle was in an odd half-mounted state (OS X is prone to dismountus interruptus).

Something worth remembering ...