Replies

I tried your suggestion, but it did not make any difference in printing email messages. (This is after several reboots as well, and IE is printing backgrounds.)

Try putting =Rand() in the cells beside your column, and then sort both columns on the second, randomly-generated column.

I wasn’t aware that they could be stuck to the desktop. For me, that is good enough. I keep Outlook in my Startup folder so that while I am at work it is always open. Therefore the “closed but still open” problem isn’t really a problem for me. The desktop is where I temporarily store a lot of “work in process” files, as well as the usual system clutter, so it is actually quite a convenient place to stick these notes.

Now that I’m aware of this option, is there a way to add Outlook Notes to the “New” menu when right-clicking the desktop?

Copy your query that counts up the number of reports people have made, but leave out the selection criteria for number of reports. This will give you the full count for every reporter. Next, create a new query that will match up your Primary SSN table to the “full count” query for unmatched records; set their count to 0. Create a union query to combine the “full count” query and the zero-report query to give the reporting count for every person. Use your report count selection criteria on this query.

Not a whole lot of finesse, but it should do the job.

I simplified the whole mess by creating a form for the user to input their criteria. This form just edits the information in a table that contains only one record. (No records can be added or deleted, only changed.) The fields from this table are pulled into the query and used as my criteria – no relationships are needed. After the user enters their choices in the form, a button-run macro closes the form and runs the desired query.

No serious coding required.

Since you are working with dates relative to when the report is actually being run, use the following formulas to get your two dates.
[indent]

---

StartDate: DateSerial(Year(Now()),Month(Now()),1)
EndDate: DateSerial(Year(Now()),Month(Now()+2),1)-1

---

[/indent]
This gives a starting date equal to the first day of the current month, and an ending date equal to the last day of the following month. These formulas can easily be built right into your query as criteria, using >= StartDate AND <= EndDate

If I follow correctly, you want the user to input a start date and end date for selecting data, and then use the resulting data in a report? If this is the correct interpretation, I have something that just might work for you.

For a very similar situation, I set up a separate table to hold the desired report dates (and other user-selectable report criteria). The query included both the source data table and the select data table, and returned only the records that matched. A form was set up to access this table, allowing the one record to be edited, but without allowing additions or deletions. After entering the dates in the form, clicking on a button to “Continue Processing” opens the report, automatically pulling the data through the query.

In order to get a match on a date range to a single date field in the data table, I did not use a relationship to select the data. Instead, I set up a criteria for the date field, referencing back to the select data table:

>=[SelectData.StartDate] AND <=[SelectData.EndDate]

This would match up the single date field stored in the main data table to both of the dates specified.

Alternately, you could add an additional field for “Alternate Name” to capture the other family name that the record should be cross-referenced against. Your query could then check to see if surname you are checking for matches either the primary or alternate name. If there is no alternate name needed for the record, the field can be left as Null.

Sample Data:

LastName	AltName	Matches If
Roe	Doe	Either
Doe	Roe	Either
Conventional	Null	Conventional

Andrew — That is the correct solution, but I think Microsoft got it wrong to begin with. How long has DOS been around, with it’s Autoexec? Us old Lotus users could make a macro and have it run automatically. (OK, it wasn’t actually called Autoexec, but the concept was the same.) Microsoft even got it right with Access when they included Autoexec as a special macro name.

So why can’t Microsoft do the logical thing with Excel?

When I was looking to create a macro that would run automatically whenever the worksheet was opened, my first thought was to try naming it “Autoexec” out of long-established habit. When this didn’t work, over the course of a few days I spent hours digging through Excel’s Help, and then the Knowledge Base, but Microsoft did not have “Autoexec” anywhere in the help file or KB — not even as a cross reference leading to “Workbook_Open()”.

I concede that writing macros is going a step or few beyond basic worksheet programming, but I think forcing users to learn VBA for something so basic as Autoexec is a little too much. Especially when Microsoft makes it so easy to actually records macros.

Apologies for this little rant; you’ll now be returned to your regularly scheduled program.

I have a similar, but not quite identical, problem. When printing, the contents of combo boxes or fields are not scrambled, but they are printed in some super wide font that I don’t recognize. Most of the time this is just a minor nuisance, since the contents of the box are usually short enough to completely print; other times, part of the contents get truncated. All font settings for IE are the install default, and the printing is on an HP1100.

It would be nice if whatever fixes your problem would help correct mine too.

By academic edition are you referring to the special agreement that Microsoft has with educational institutions, or what was characteristically a low-cost but functionally-castrated version of a commercial program?

I bought my Office 2000 Pro for $10.00, and I havn’t found any differences in the actual software between it and the full-price versions. The only difference that I could easily see was in the EULA — due to the special pricing agreement, I’m not even allowed to give the things away if I ever stop using them. (Presumably, to avoid impoverished university students from creating a “black market” in legal, discount-priced Microsoft software.)

I forget the reasoning given when the deal was first announced, but it makes sense for Microsoft. Get universities to run virtually nothing but Office products, make the software affordable to students, and get us hooked on Microsoft. Logically, making substandard software available would undermine this program, so what we get sure seems to be the real deal.

Note to MaryJ — I’ve upgraded for the service releases, and have had no problems at all.

Old DOS method that I have used:

c:dir *.* /s > c_drive.txt

This should, if I remember correctly, give you a listing of all files on your hard drive, organized into their directories, and stuff it all into a text file that you can print out or otherwise manipulate. Do this before and after your maintenance work, and you should easily be able to compare the two files for changes.

I use Monarch to handle text files similar to yours. This is not an Office, or even a Microsoft, product but comes from Datawatch (http://www.datawatch.com). It allows you to set up a template to trap text that falls into specific patterns and convert it into data tables. There is quite an array of functions & filters you can use from within Monarch, and it supports exporting the table-ized data into spreadsheet or database formats (including Excel and Access).

For me, Monarch provides the backbone for converting large amounts of printed report data into functional data. It may be worth your time to check it out.

Simple way, which will keep your query flexible enough for future use, would be to put the following on the criteria line for the date field in the delete query:

<=[Enter Date to delete records from]

Whenever you run the query, it will prompt you to enter a date, and then delete all records where the date field is less than or equal to the input date.

I received a tip from ElementK Tips (http://www.elementktips.com) that looks as if it would be exactly what you are looking for. Since their tips are copyrighted, I don’t believe it would be proper (or legal) to repost it in its entirety here. If you can’t find it in their archive of tips, I could forward it to you directly.

Here is the raw code that was given in the tip, if that would be enough:
[indent]

---

Function PreventBypass() As Boolean
Set prp = CurrentDb.CreateProperty(“AllowBypassKey”, _
dbBoolean, False, True)
CurrentDb.Properties.Append prp
Set prp = Nothing
End Function

---

[/indent]