Effecting googling.

Learn to google. Specifically, how to be very specific -- when, um, googling.

Two of my favorite time-savers include
1. forcing a phrase - extremely useful when your troubleshooting errors or code exceptions) ... Searching for
SYMEVENT.SYS ( SYMEVENT+7a60 )
and
"SYMEVENT.SYS ( SYMEVENT+7a60 )"
will get you very different results.

2. specifying a website in which to look for said results ("hiring manager" site: www.gsiwatersolutions.com).

3. making data mandatory: +

4. or ... negatory? -

Here are some search strings we might us poking around for help or existing code to get us started on a project:

access scripting

http://www.google.com/search?source=ig&hl=en&rlz=&=&q=access+scripting

16,700,000 results.

msaccess vba

http://www.google.com/search?hl=en&q=msaccess+vba+&aq=f&oq=&aqi=g%3As10

1,680,000 results.

access vba site:*.microsoft.com

http://www.google.com/search?hl=en&q=access+vba+site%3A*.microsoft.com
33,400 results that are organized better than MSDN organizes them.

Another good source -- groups.google.com.

Tips credited to Christian Graus. Awesome.
http://www.codeproject.com/KB/tips/HowToUseGoogle.aspx

...and from the Oracle herself:
http://www.google.com/support/websearch/bin/answer.py?answer=136861

http://www.googleguide.com/crafting_queries.html
http://www.googleguide.com/using_advanced_operators.html