Replies

Regarding the idea of dragging Outlook items into Explorer windows…We used to do this a lot, but there are drawbacks. The filename is generated from the email’s subject line and the last modified date is the date you do the drag and drop, not the received date. So if you drag a set of replies to the same email (for example), they end up in Explorer only distinguished by a number that Windows Explorer appends to the filename (if you drag them all at once, that is – if you drag another reply in later, you get the standard Explorer “do you want to replace the existing file” dialog, which is no use at all). So you’ve lost all the things that might help you navigate if you were still in Outlook – date order, sent by, etc… We tried to address this by making people stick the email’s date into the subject line before dragging into Explorer, but that’s not ideal. So this is probably OK if you’re simply required to archive your emails for legal reasons or whatever, but not if you’re likely to want to work with them in the future.

That’s an idea. I use user-level security now to do things like preventing guests changing the data, but I could use it to disable certain modules and forms that guests aren’t allowed to use. However, I would like to alter the user interface in a more user-friendly way too, instead of leaving controls enabled for guests to try, and letting the User Level Security send its unfriendly messages.

Sort of… The export specification doesn’t seem to have a “Code Page” option, but it does have a “File Origin” option (this is Access 97). The choices are “Windows (ANSI)” and “DOS or OS/2 (PC-8)”. Using the first one in a manual export produces the “plus-or-minus” (character 00B1) and using the second one produces the “n-tilde” (character 00F1). So it sounds like there may be a way forward there. I haven’t yet managed to produce an export specification for the specific query, because the query design includes query fields of the form MyTable1.SameFieldName and MyTable2.SameFieldName, and the wizard can’t cope, but that’s another story (I guess I can rename the fields in the query using SQL “AS” or it’s Design Grid equivalent).

Sort of… The export specification doesn’t seem to have a “Code Page” option, but it does have a “File Origin” option (this is Access 97). The choices are “Windows (ANSI)” and “DOS or OS/2 (PC-8)”. Using the first one in a manual export produces the “plus-or-minus” (character 00B1) and using the second one produces the “n-tilde” (character 00F1). So it sounds like there may be a way forward there. I haven’t yet managed to produce an export specification for the specific query, because the query design includes query fields of the form MyTable1.SameFieldName and MyTable2.SameFieldName, and the wizard can’t cope, but that’s another story (I guess I can rename the fields in the query using SQL “AS” or it’s Design Grid equivalent).

Does this mean that queries using “*” written in Access97 for the Jet Database Engine will fail to work if I convert my database to use ADO as part of a port to Access2002/XP?