Hi Doug, The License manager clearly shows 4D Developer Professional v17 - Partner Program … which includes 1 (unlimited)4D Write - 4D Write Pro license.
So I’m not sure what I am doing wrong? In edition to why 4D Write Pro is returning the license error I’m a little confused about 4D Write Pro Migration process. Anyway, that’s in another NUG thread. I’ll look at it later after I do some other client work. Appreciate, John… > On May 15, 2019, at 7:57 AM, Douglas von Roeder <dvonroe...@gmail.com> wrote: > > John: > > "And "$wpDoc:=WP New” generates the same error.” > OK, understood. That’s an error because it should be returning a 4DWP object. > > My question about passing an empty BLOB stems from the docs which indicate > that you can’t pass a parameter that doesn’t have content. I suspect that > would give an error other than 9949. > > -- > Douglas von Roeder > 949-336-2902 > > > On Tue, May 14, 2019 at 5:14 PM John J Foster <trueg...@isomedia.com > <mailto:trueg...@isomedia.com>> wrote: > Hi Doug, > > Yes the BLOB is empty. > > I upgraded a client from 4D 2012 (windows) to 4D v17. However in the v12 > version the 4D Write docs were still being saved in a picture field. The 4D > Write Pro migration tools specifically is designed too handle converting > those Write pictures to Write Pro objects. OT so I thought! > > But it’s receiving a picture field and returning no BLOB to give to the 4D > Write Pro doc. > > So… > > John... > > >> When I look at the docs for WP New, $1 is a optional parameter. If passed as >> a BLOB, the content of the BLOB should be either a 4D Write Pro document or >> a 4D Write document. It doesn’t appear that an empty BLOB is acceptable as a >> parameter. I might have missed it in the earlier email but is your $blob >> contain a document or is it just an empty BLOB? >> >> -- >> Douglas von Roeder >> 949-336-2902 >> >> >> On Tue, May 14, 2019 at 4:41 PM John J Foster via 4D_Tech >> <4d_tech@lists.4d.com <mailto:4d_tech@lists.4d.com>> wrote: >> Hi Pat, >> >> Yes $blob has been defined in each method. >> >> And "$wpDoc:=WP New” generates the same error. >> >> John… >> >> > >> > Has $blob been defined? >> > Do you get the error if you call: >> > >> > $wpDoc:=WP New >> >> ********************************************************************** >> 4D Internet Users Group (4D iNUG) >> Archive: http://lists.4d.com/archives.html >> <http://lists.4d.com/archives.html> >> Options: https://lists.4d.com/mailman/options/4d_tech >> <https://lists.4d.com/mailman/options/4d_tech> >> Unsub: mailto:4d_tech-unsubscr...@lists.4d.com >> <mailto:4d_tech-unsubscr...@lists.4d.com> >> ********************************************************************** > ********************************************************************** 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 **********************************************************************
