Peter Miller <pmiller@pksolutions.com> wrote in message news:<plsd801qk1nda0uvp4tjdij3oif1rn1shu@4ax.com>. ..[color=blue]
> On Wed, 21 Apr 2004 21:02:38 GMT, Tony Toews <ttoews@telusplanet.net>
> wrote in comp.databases.ms-access:
>[color=green]
> >Your network admin guy is an idiot. If you were dealing directly with the exchange
> >files under the hood so to speak, I'd agree with him. But you are using the standard
> >Microsoft interfaces so this isn't a problem. You are using the same interfaces that
> >Outlook and other software uses. So not a problem.[/color]
>
> I'd second Tony's comments, but with a caveat.
>
> Tony is absolutely correct about raw file i/o versus working through
> Jet, but its important to add that just because you are using Jet for
> accessing email rather than your own home grown raw file i/o doesn't
> mean you're using Jet wisely, or in a fashion that could not result in
> just the outcome this network guy warned against.
>
> Let's take a simple example. You want to display header information
> for sent messages, so you create a query that does what you want, and
> use it as the data source for a given interface element. This is what
> Outlook does anyway, so no problems, right? Well, what if Outlook
> pulled in a snapshot, and created a separate transparent transaction
> for editing, and you pulled back an editable recordset? You both get
> the same results and functionality, except that if Exchange needed to
> write new data out, it might be blocked by your program, but would
> have been fine with the interaction of Outlook alone.
>
> Just my 2c.
>
> Peter Miller
> __________________________________________________ __________
> PK Solutions -- Data Recovery for Microsoft Access/Jet/SQL
> Free quotes, Guaranteed lowest prices and best results
>
www.pksolutions.com 1.866.FILE.FIX 1.760.476.9051[/color]
Peter and Tony, thanks for the response. But let me clarify. The
four things I am doing are:
Creating a new email which obviously would be specific to the person
running the code.
Creating a new calendar item in a public folder.
Creating a new task item in a users private task folder.
Lastly, I have linked a sent items folder with my database, using the
wizard. I just realized I could link any Exchange folder as well
using the wizard, darn, sometimes they make this sooooo easy. (Not
that I have thought how I would use this yet, but would youz two be
against it?)
It's the last one that I think my guy was most worried about and I
think Peter warned against. I obviously don't need to edit anything
in my sent items folder thru my database so is there away I could make
it uneditable, if it isn't already and would that be enough to avoid
any problems?
