[AccessD] OutputTo

Doug,

I came across this a couple of months ago.  And yes it's a pain.  I called
Microsoft Help after convincing myself it was truly a bug.  Lo and Behold,
they have fixed this in Access 2003!  No plans to fix for Access 2002.

Wish my news was better!

Dan 

PS - Because this was truly a bug, MS did not charge me for the call.


-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Doug Murphy
Sent: Friday, February 10, 2006 6:21 PM
To: 'Access Developers discussion and problem solving'
Subject: [AccessD] OutputTo

Folks,

This is an FYI. Maybe it will save some one some time or one of you can
explain the cause.  I use the snapshot functionality in Access so folks can
send formated copies of reports (Yes I am converting to a built in pdf
creator, but for now snapshots work and I don't have to buy anything)  Have
had good luck with the snapshots since we convereted our runtime to Access
2002.  

Today a customer called that we did a customization for to say that the
output report as snapshot was giving an error of "The report snapshot was
not created because you don't have enough free disk space .....". I can
creat the error on my development machine.  Checked the usual problems of
faulty path, illegal characters, etc, and not satisfaction.  I then started
playing with the length of the file path.  Turns out if the path length,
including the snapshot file name and extension is longer than 126 characters
you get the error.  If the length is 126 or less it works as advertised.
Weird!

If anyone has a reason for this behavior I'd appreciate your thoughts.

Doug

-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com