Disk I/O errors should always be logged, including secret folders. If
you were not allowed to log that error, better leave the company
before the errors hurt your reputation and career. Find a regular job
that's normal. :)
On Fri, Jun 28, 2019 at 4:57 AM Tracy Pearson wrote:
>
> Once had a networ
I would always exercise caution in all file i/o codes and walk that
distance!! I would argue with my boss about that extra distance.
Anyway, the problem might bite you again, or someone in place of you.
Good luck then! :)
On Fri, Jun 28, 2019 at 4:38 AM Fletcher Johnson
wrote:
>
> We did have a
s...
Tracy
-Original Message-
From: ProfoxTech [mailto:profoxtech-boun...@leafe.com] On Behalf Of Fletcher
Johnson
Sent: Thursday, June 27, 2019 4:37 PM
To: profoxt...@leafe.com
Subject: RE: Odd Error Message
We did have a test to see if the temp folder existed. If it didn't we tried
t
m/athletes/fletcherjohnson
408-946-0960 - work
408-781-2345 - cell
-Original Message-
From: ProFox [mailto:profox-boun...@leafe.com] On Behalf Of Man-wai Chang
Sent: Thursday, June 27, 2019 4:23 AM
To: ProFox Email List
Subject: Re: Odd Error Message
You better double-check the err
You better double-check the error handler! It should not have ignored
the write error to that TEMP folder.
To verify whether a folder was writable, you could test write then
delete a file in that folder and look for errors. You might need to
temporarily use ON ERROR to trap file write errors befor
com] On Behalf Of Tracy Pearson
Sent: Tuesday, June 25, 2019 6:30 AM
To: profox@leafe.com
Subject: RE: Odd Error Message
Hello Gene,
That just raises more questions about what COM object is being used to
create the XLS file.
Is it shipping with the latest Windows 10 computer?
Is it built in to the
At 06:30 2019-06-25, "Tracy Pearson" wrote:
Hello Gene,
That just raises more questions about what COM object is being used to
create the XLS file.
Is it shipping with the latest Windows 10 computer?
Is it built in to the VFP runtimes?
Is this functionality suddenly going to stop working one da
m] On Behalf Of Ted
Roche
Sent: Tuesday, June 25, 2019 10:34 AM
To: profoxt...@leafe.com
Subject: Re: Odd Error Message
What Alan said. When TYPE XL5 was introduced, it was added because Excel 5
changed the output file format to some COM-based structured storage, iirc.
So, VFP is calling some Windo
What Alan said. When TYPE XL5 was introduced, it was added because Excel 5
changed the output file format to some COM-based structured storage, iirc.
So, VFP is calling some Windows OS-based API calls to create the storage,
as it should, and that API gracefully fails ("0x80030003") when you are
try
I would imagine the functionality is baked into the VFP runtimes, I've never
had an issue with it failing on any version of Windows, even without Excel
installed.
--
Alan Bourke
alanpbourke (at) fastmail (dot) fm
___
Post Messages to: ProFox@leaf
Hello Gene,
That just raises more questions about what COM object is being used to
create the XLS file.
Is it shipping with the latest Windows 10 computer?
Is it built in to the VFP runtimes?
Is this functionality suddenly going to stop working one day after the DLL
is identified and removed by s
11 matches
Mail list logo
