- Roundtable - muug.ca

Access Annoyances Needed for New Book (fwd)
by gedetil＠cs.umanitoba.ca 01 Jul '04

01 Jul '04

Just FYI, in case any of you are interested in contributing you favourite MS Access annoyance(s) to the book... -- Gilbert E. Detillieux E-mail: <gedetil(a)cs.umanitoba.ca> Dept. of Computer Science Web: http://www.cs.umanitoba.ca/~gedetil/ University of Manitoba Phone: (204)474-8161 Winnipeg, MB, CANADA R3T 2N2 Fax: (204)474-7609 ---------------------------------------------------------------------------- From: marsee(a)oreilly.com To: gedetil(a)muug.mb.ca Subject: Access Annoyances Needed for New Book Date: Wed, 30 Jun 2004 17:52:33 -0700 Dear User Group Leader: O'Reilly is pulling together a new book called "Microsoft Access Annoyances" and, once again, we'd like your help! As you might guess, "Access Annoyances" ponders the problems, snarls, quirks, bugs, and just dumb things about Access that drive users nuts. The annoyances will encompass a range of topics: the Access interface, entering data, queries, reporting hassles, VBA, moving data to and from Excel and SQL databases, data tables, expressions, macros, deployment, security--well, you get the idea. If any members of your group use Access--be they newbies or Access masters--and they have annoyances they'd like to see solved, have them email marsee(a)oreilly.com with "Access Annoyances" in the subject line. Just have them note what version of Access and Windows they're using. As always, thanks for sharing. We'll make sure to get copies of "Access Annoyances" sent to your group shortly after publication. --Marsee *** An example: Long Lines In Small Places THE ANNOYANCE: I'm trying to type a long expression into a tiny text box, which is about as much fun as trying to watch a movie with a couple of basketball players seated in front of you. How the heck do you keep track of what you're typing when you can only see two or three words at a time? THE FIX: One of Access' handier features is the zoom box. Hit <Shift F2>, and Access opens a big, empty text area for editing a long line of text. You can use this trick just about anywhere you see a text box: in the query design grid, in property sheets, in a table design window or datasheet. For that matter, your users can benefit from this trick, too--it works on form fields as well. Highly recommended. [TIP: You'll notice that the zoom box closes when you hit <Enter>. If for some reason, you absolutely need a line break in what you're typing, use <Ctrl-Enter> instead.] ***

1 0

Looking to purchase Cisco 2500 series Routers
by Michael J. Dikkema 27 Jun '04

27 Jun '04

Hi, All. I hope nobody minds me posting this. I'm looking to purchase some used Cisco 2500 series routers for a lab environment. I would need 16mb DRAM and 16mb Flash, and would be looking for DTE-DCE serial cables and ethernet transceivers as well. If anyone has any they're willing to part with, please send me an email off-list. Thanks.

1 0

From eWeek: Linux Enterprise Grip Tightens with EU Wins
by gedetil＠cs.umanitoba.ca 18 Jun '04

18 Jun '04

A more detailed article on EU civic governments adopting open source... http://www.eweek.com/article2/0,1759,1613842,00.asp -- Gilbert E. Detillieux E-mail: <gedetil(a)cs.umanitoba.ca> Dept. of Computer Science Web: http://www.cs.umanitoba.ca/~gedetil/ University of Manitoba Phone: (204)474-8161 Winnipeg, MB, CANADA R3T 2N2 Fax: (204)474-7609

1 0

From ZDnet: Munich to stick with open source
by gedetil＠cs.umanitoba.ca 18 Jun '04

18 Jun '04

This might be of interest to you open-source fans... http://zdnet.com.com/2100-1104_2-5237356.html -- Gilbert E. Detillieux E-mail: <gedetil(a)cs.umanitoba.ca> Dept. of Computer Science Web: http://www.cs.umanitoba.ca/~gedetil/ University of Manitoba Phone: (204)474-8161 Winnipeg, MB, CANADA R3T 2N2 Fax: (204)474-7609

1 0

Re: [RndTbl] up2date and yum updates for CORE 2
by gedetil＠cs.umanitoba.ca 10 Jun '04

10 Jun '04

According to Mel Seder: > I went to our site http://www.muug.mb.ca/fedora-updates.html and read it and > then downloaded the two patch files. I read about the patch command in > "Running Linux" published by O'Reilly as well as running and reading "info > patch". > > As I recall, for CORE 1 I just went in and edited sources (maybe yum.conf > also) by hand because I didn't realize that what the gobbly gook in the patch > file did or that I even needed the patch command. > > I generated a patch file to update a phone list text file just to see how patch > worked and it worked how I expected. I did not understand everything in > "Running Linux" or "info patch" but the following is what I think I should do. > > both patch files are in ~ > > I issue "su" from ~ for root access > > #patch < rhn-sources-fc2.patch > #patch < yum.conf-fc2.patch > > Am I missing something or should the above work? I would do the following: cp -p /etc/sysconfig/rhn/sources /etc/sysconfig/rhn/sources.FC2 cp -p /etc/yum.conf /etc/yum.conf.FC2 patch -p0 < rhn-sources-fc2.patch patch -p0 < yum.conf-fc2.patch The first two commands will just make backup copies of the config files before you patch them. (I've gotten into the habit of saving a copy of each original configuration file before modifying it for the first time. That way, I can always go back to the original, or use "diff" to find out what has changed.) There is a patch option to save a backup of the file before patching it, but I can never remember what the option is, and it seems to behave slightly differently depending on what version of patch you have. So, I find it simpler to just make my own copies first (which I do out of habit already). Also, on some versions of patch, the backup copy is made without preserving the modification time stamp. I'm anal about these things, and I like my backups to have an accurate time stamp, which is why I always use "cp -p". > What I think I will do, just cause I'm chicken, is run the following before > the actual/live patches; > > #patch --dry-run < rhn-sources-fc2.patch > sources.dryrun > #patch --dry-run < yum.conf.fc2.patch > yum.dryrun Sure, that would be a safe way to try things out first, but of course, if you've made your backup copies, then you can be a bit more brave! :) I wasn't even aware of the --dry-run option. It appears to be in GNU patch (even older versions), but wasn't in the original patch command written by Larry Wall (better known as the author of perl), nor is it in the Solaris patch command. > I'm mostly concerned about the patch commands. Should they work or are other > parameters needed? Not sure about the patch command that comes with FC2, but in some earlier versions, you had to specify at least some options in order to use it in non-interactive mode. Otherwise, it would insist on prompting you for file names, etc. So, the "patch -p0 < patch_file" command is something I also now do out of habit. (Strictly speaking, -p0 should happen by default, i.e. it tells patch not to strip any directory prefixes from the pathnames in the patch file, in order to find the correct files to patch. But in some versions, that option also told it to pull the file names from the patch file, rather than asking for them.) -- Gilbert E. Detillieux E-mail: <gedetil(a)cs.umanitoba.ca> Dept. of Computer Science Web: http://www.cs.umanitoba.ca/~gedetil/ University of Manitoba Phone: (204)474-8161 Winnipeg, MB, CANADA R3T 2N2 Fax: (204)474-7609

2 2

up2date and yum updates for CORE 2
by Mel Seder 10 Jun '04

10 Jun '04

I went to our site http://www.muug.mb.ca/fedora-updates.html and read it and then downloaded the two patch files. I read about the patch command in "Running Linux" published by O'Reilly as well as running and reading "info patch". As I recall, for CORE 1 I just went in and edited sources (maybe yum.conf also) by hand because I didn't realize that what the gobbly gook in the patch file did or that I even needed the patch command. I generated a patch file to update a phone list text file just to see how patch worked and it worked how I expected. I did not understand everything in "Running Linux" or "info patch" but the following is what I think I should do. both patch files are in ~ I issue "su" from ~ for root access #patch < rhn-sources-fc2.patch #patch < yum.conf-fc2.patch Am I missing something or should the above work? What I think I will do, just cause I'm chicken, is run the following before the actual/live patches; #patch --dry-run < rhn-sources-fc2.patch > sources.dryrun #patch --dry-run < yum.conf.fc2.patch > yum.dryrun I'm mostly concerned about the patch commands. Should they work or are other parameters needed? Can anyone see any problems or make any suggestions? ===== The true measure of a man is how he treats someone who can do him absolutely no good. -Samuel Johnson, lexicographer (1709-1784)

1 0

pitty the Royal Navy
by ed orphan 10 Jun '04

10 Jun '04

According to today's BBC ( June 10, 2004 ), the new Type 45 "stealth" destroyers, which are to "provide the future backbone of the Royal Navy" are to be "controlled by state-of-the-art computers using a Windows NT operating system." BAE Systems is to have the first one launched in September 2007. A price of $ 3.6 billion is stated, but its not made clear if that's for all 26 of them, or just one. I suspect its for just one. Either way, it's good money pissed away. Windows NT ! These things will be a menace to everyone, including their own crews.

2 1

Fedora 2 screen blanking
by Mike Pfaiffer 09 Jun '04

09 Jun '04

Installed Fedora 2 last week. One of the things I did (after having it boot into mode 3 and going into KDE when starting X) was to disable the various (forced) power management tools and screen saver. Today I was away from my machine for a few minutes and saw a blank screen. The monitor was indicating there was no signal. Since I disabled power management in the CMOS as well, I must have missed something. After a couple of hours looking at the usual places I figure I am missing something. Any suggestions where else to look? Later Mike -- +----------------------------------------------------------------------+ | Digital Civilization magazine: http://www.digitalcivilization.ca | |Call-A.P.P.L.E. and the Digital Civilization http://www.callapple.org | | http://members.shaw.ca/pfaiffer = Mike Pfaiffer (B.A., B.Sc.) | +----------------------------------------------------------------------+ ----- BEGIN GEEK CODE BLOCK ----- Version: 3.12 GCS/G/IT/PA/SS d s+:- a? C++ UL L++ W++ N++ o+ K- w(---) O+@ M++@ V PS+ PE !PGP t+ 5+ X R tv b+ DI+++ D++ G e++* h! r-- !y-- UF++ ------ END GEEK CODE BLOCK ------

1 0

[Fwd: [Sean's Obsessions] New Comment Posted to 'Linux Unwired']
by Sean A. Walberg 05 Jun '04

05 Jun '04

One of the authors of Linux Unwired sent me this: -----Forwarded Message----- Name: Roger Weeks Just a quick note: the authors (yes I am one) have a blog at http://www.linuxunwired.com. You can find out where we are speaking, read errata and coming soon, new stuff we couldn't fit in the book. -- Sean A. Walberg <sean(a)ertw.com> http://www.ertw.com

1 0

Linux Unwired review
by Sean A. Walberg 04 Jun '04

04 Jun '04

I put up a review of "Linux Unwired": http://ertw.com/blog/archives/linux_unwired-260504.html A hell of a book if you're looking for information on all things wireless for Linux. Sean -- Sean A. Walberg <sean(a)ertw.com> http://www.ertw.com

1 0