Append general - error in the DLL

To print a data field derived .jpg file, the following code has worked well
in the past but now produces an OLE error code 0x800401f9: Error in the DLL.

create cursor PHOTO ( entry G )
append blank
append general entry from &photopath\&orignam..jpg

where photopath and orignam are path and filename for the JPEG file to be
printed with other text and graphics in a report.

I suspect the problem may be to do with a printer driver change but
unloading all printer drivers makes no difference. Any ideas?

Dan
Tue Nov 29 13:44:30 CST 2005

For starters, I'd change the &macros to a (name expression). You might be
encountering a problem caused by spaces in paths otherwise.

append general entry from (photopath + orignam + ".jpg")

That said, if you already have a jpg on disk why use the general field at
all? Just put the file itself in an image control on the report.

Dan


mitch wrote:
> To print a data field derived .jpg file, the following code has
> worked well in the past but now produces an OLE error code
> 0x800401f9: Error in the DLL.
>
> create cursor PHOTO ( entry G )
> append blank
> append general entry from &photopath\&orignam..jpg
>
> where photopath and orignam are path and filename for the JPEG file
> to be printed with other text and graphics in a report.
>
> I suspect the problem may be to do with a printer driver change but
> unloading all printer drivers makes no difference. Any ideas?

mitch
Tue Nov 29 14:23:06 CST 2005

Dan,

Thanks for reply. Using name expression makes no difference. I am stil
confused as to why the process worked reliably before - still, I will work
out a way to use the filename direct.

"Dan Freeman" wrote:

> For starters, I'd change the ¯os to a (name expression). You might be
> encountering a problem caused by spaces in paths otherwise.
>
> append general entry from (photopath + orignam + ".jpg")
>
> That said, if you already have a jpg on disk why use the general field at
> all? Just put the file itself in an image control on the report.
>
> Dan
>
>
> mitch wrote:
> > To print a data field derived .jpg file, the following code has
> > worked well in the past but now produces an OLE error code
> > 0x800401f9: Error in the DLL.
> >
> > create cursor PHOTO ( entry G )
> > append blank
> > append general entry from &photopath\&orignam..jpg
> >
> > where photopath and orignam are path and filename for the JPEG file
> > to be printed with other text and graphics in a report.
> >
> > I suspect the problem may be to do with a printer driver change but
> > unloading all printer drivers makes no difference. Any ideas?
>
>
>

Dan
Tue Nov 29 16:17:48 CST 2005

What changed in your installation/configuration?

Handling of general fields isn't done by VFP. It hands ALL I/O off to the
owner, the OLE server app that owns that data type. All your app can do is
say "Hey you! Handle this." If the server doesn't (because of some update)
all your app can do is say "Oh well."

Dan

mitch wrote:
> Dan,
>
> Thanks for reply. Using name expression makes no difference. I am
> stil confused as to why the process worked reliably before - still, I
> will work out a way to use the filename direct.
>
> "Dan Freeman" wrote:
>
>> For starters, I'd change the ¯os to a (name expression). You might be
>> encountering a problem caused by spaces in paths otherwise.
>>
>> append general entry from (photopath + orignam + ".jpg")
>>
>> That said, if you already have a jpg on disk why use the general
>> field at all? Just put the file itself in an image control on the
>> report.
>>
>> Dan
>>
>>
>> mitch wrote:
>>> To print a data field derived .jpg file, the following code has
>>> worked well in the past but now produces an OLE error code
>>> 0x800401f9: Error in the DLL.
>>>
>>> create cursor PHOTO ( entry G )
>>> append blank
>>> append general entry from &photopath\&orignam..jpg
>>>
>>> where photopath and orignam are path and filename for the JPEG file
>>> to be printed with other text and graphics in a report.
>>>
>>> I suspect the problem may be to do with a printer driver change but
>>> unloading all printer drivers makes no difference. Any ideas?

Matthew
Tue Nov 29 12:02:15 CST 2005

I see these from time to time, and it's usually a corrupt file causing it.
Also, the association for jpg files may have changed.

"mitch" <mitch@discussions.microsoft.com> wrote in message
news:3224A835-BCB3-4717-ADA5-A01322E1C37C@microsoft.com...
> To print a data field derived .jpg file, the following code has worked
> well
> in the past but now produces an OLE error code 0x800401f9: Error in the
> DLL.
>
> create cursor PHOTO ( entry G )
> append blank
> append general entry from &photopath\&orignam..jpg
>
> where photopath and orignam are path and filename for the JPEG file to be
> printed with other text and graphics in a report.
>
> I suspect the problem may be to do with a printer driver change but
> unloading all printer drivers makes no difference. Any ideas?
>
>

Matthew
Tue Nov 29 16:18:20 CST 2005

Is the image corrupt? Has the association to jpg file on the machine
changed? Those are the two things I see cause this problem.

"mitch" <mitch@discussions.microsoft.com> wrote in message
news:E5EC38D0-3800-4205-AA51-592A72E06F4C@microsoft.com...
> Dan,
>
> Thanks for reply. Using name expression makes no difference. I am stil
> confused as to why the process worked reliably before - still, I will work
> out a way to use the filename direct.
>
> "Dan Freeman" wrote:
>
>> For starters, I'd change the ¯os to a (name expression). You might be
>> encountering a problem caused by spaces in paths otherwise.
>>
>> append general entry from (photopath + orignam + ".jpg")
>>
>> That said, if you already have a jpg on disk why use the general field at
>> all? Just put the file itself in an image control on the report.
>>
>> Dan
>>
>>
>> mitch wrote:
>> > To print a data field derived .jpg file, the following code has
>> > worked well in the past but now produces an OLE error code
>> > 0x800401f9: Error in the DLL.
>> >
>> > create cursor PHOTO ( entry G )
>> > append blank
>> > append general entry from &photopath\&orignam..jpg
>> >
>> > where photopath and orignam are path and filename for the JPEG file
>> > to be printed with other text and graphics in a report.
>> >
>> > I suspect the problem may be to do with a printer driver change but
>> > unloading all printer drivers makes no difference. Any ideas?
>>
>>
>>