In article <
f958d865-ea5b-763c...@gmail.com>,
[Snip]
> Hi Dave
> Fireworkz, like PipeDream, has separate internal types for numbers and
> date/times, text strings etc. There's currently no way to get Fireworkz'
> style system to treat one as the other (I see a way to do that if
> required).
> It relies on the import from Excel code to recognize cells with
> appropriate date/time formatting and compose the analogous Fireworkz
> formatting codes before then deciding to convert the imported number to
> a date/time. If you could let me have an Excel sample, cut down as
> necessary, which doesn't convert, I'd be grateful.
> Stuart
> --
> Stuart Swales
Stuart, thanks for getting back...
As per your above request, I decided to make a new small sample Eureka to
Excel export file for you
I then dropped it into Fireworkz and miracles, everything Date and time
was displayed correctly...
Ooeer! What's going on here?
I took the Eureka to Excel export file I'd used earlier in the day, but
when dropped in Fireworkz, this one has the chaos Dates and times.
Why I asked myself, and after some thought, did a couple of experiments
and revealed the answer.
Earlier today I'd exported Eureka to Excel in Excel 3 format, to keep
things simple. (That's the one that fails date and time.)
This evening, I'd use the Eureka to Excel export in Excel 4 format, and
this is the one that worked.
So it seems, not a Fireworkz problem as such just an export quirk from
Eureka.
I'm now sorted.
Thanks
Dave
PS: If you'd still like a copy of a bit of the errant Excel 3, Eureka to
Excel export file I can still send.
Or even the Excel 4 to compare.
D.
--
Dave Triffid