Hi All,

There’s an implied assumption that Migrating 4d-write documents stored in 
picture fields will work using the v17 component. I didn't see any caveats as 
to preparing 4D Wrote docs in earlier versions.

So, as Randy offered, maybe that’s the correct path. Maybe I should change the 
docs in 4D v12 from picture fields into blob - either by adding another blob 
fold to the table or exporting the 4D Write docs to disk.

Is this the best way to approach 4D Write docs?

Have others had a similar experience as Randy?

Thanks for your help,

> 4D v17R4 Windows and Macintosh Stand alone and 4D Server
> I do not have an old 4D Write plugin only the new 4D Write Pro
> App upgraded from 4D 2012 to 4D V17
> I am working on the final v17 conversion piece migrating older 4D Write saved 
> in picture field to 4D Write Pro saved in object field. I am using the the 
> code from the component on the blog 
> "https://blog.4d.com/migrate-4d-write-documents-stored-in-picture-fields/#component”.
> However, as I watch the code in the debugger, this is what I see:
> $blob:=_Extract4W7From4DPicture ($1)
> If (BLOB size($blob)=0)
>       GET PICTURE FORMATS($1;$codecIDs)
>       If (Size of array($codecIDs)=1)
>               If ($codecIDs{1}=".pict”)
>               !!! // makes it to here so “knows” it’s a pict.
>                       $blob:=_Extract4W7FromMacPicture ($1)
>               !!! // returns an empty blob
>               End if 
>       End if 
> End if 
> Inside this routine "Extract4W7FromMacPicture ($1)” this line executes
> PICTURE TO BLOB($1;$blob;"PICT") 
> Always returns an empty blob even though $1 is a picture with a size like 
> 25ko.
> So not sure what;’s going on and why it doesn’t work.
> Does anyone have any experience with converting an older 4D Write saved in a 
> picture field into a 4D Write Pro object?
> Appreciate,
> John…

4D Internet Users Group (4D iNUG)
Archive:  http://lists.4d.com/archives.html
Options: https://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:4d_tech-unsubscr...@lists.4d.com

Reply via email to