Tagged connection

LinkedIn.com: Just a giant back-patting circle?

The new thing in career ‘connections’ is LinkedIn.com, the website that allows you to add colleagues and former classmates to your own personal network, for the purpose of furthering your career and opening new avenues through the people you already know. On the face of it, LinkedIn seems kind of neat–you can list all the people you work with as ‘Connections,’ create a network of people you ‘trust’ as business contacts, and even track down old classmates to see if you have a better job than they do. There’s also one other thing: you can write recommendations for your connections, which will appear in their profile after they approve them. In other words, people can comment on the quality of your work, and you can then choose whether or not to let that appear in your profile. Not surprisingly, there are quite a few glowing recommendations out there, and little to no criticism.

This raises the question in my mind as to whether or not LinkedIn truly goes beyond the level of mere facebook-style messaging and casual communication to become a vehicle for business, and not just social, networking. Admittedly, it is fun to see how many people consider you their colleague, not to mention how many people are willing to scratch your back with a positive recommendation, fully aware that the favor could be quickly and easily returned, and if the product is unsatisfactory, blocked from public view. However, I can’t imagine that prospective employers or anyone that doesn’t know the individual personally would take any useful information from this site, as it’s so heavily slanted in favor of member control over reviews and recommendations.

linkedin, social networking, facebook, myspace, business, connection, colleague, review, profile

Microsoft Access 2003 problem: cannot run reports when connected to networked printers

Microsoft Access 2003

There is a bug/weakness in Microsoft Access 2003 that I have come across recently, and it’s an insidious one. Basically, the problem manifests itself as an inability to run user-generated reports from a database. Everything else works fine–the connection to the database itself is sound, the user can run queries, view data, and do everything else imaginable except run a report.

The solution is maddeningly simple once you figure it out, but it took me quite a while to get there, so maybe I can spare some other people the time: Access runs reports via the printer driver of the default printer, and for some reason, if that printer is a networked printer, Access can’t generate the report. Queries, as a simple data-retrieval operation, do not require the driver–it’s only used in the context of the user-defined, formatted view offered by Access reports. This seems remarkably stupid, since a database application needs to run in an enterprise environment, and that implies networked laser printers.

The workaround, of course, is to install the printer locally. To do this, choose local, rather than networked at the first add printer splash screen. Then, add a local port as the name of the printer on your network, i.e. \\printers\treekiller, or through the IP, and voila, you’re connected in a way that Access 2003 understands. Seems a bit foolish, doesn’t it?