Re: unicode, blobs, and the web
Thank you for that explanation, Miyako! From: Keisuke Miyako via 4D_Tech <4d_tech@lists.4d.com> Cc: Keisuke Miyako > 2019/08/29 12:31ÅAwebmaster namethatplant.net > ÇÃÉÅÅ[Éã: > > I still have a question. > The write-up for PROCESS HTML TAGS contains the warning, "It is now highly > inadvisable to store texts in BLOBs". > > I don't use the command "PROCESS HTML TAGS" but I have used BLOB variables in > several other places throughout my website. These don't contain any > troublemaker characters and they are working well. > > Do I need to convert them to text variables? storing text in BLOB is inadvisable for several reasons: BLOBs are not ref-counted and memory inefficient. there are copied when passed as a method argument, for example. BLOB to text conversion is costly, especially when the storage encoding is not UTF-8 (unicode to unicode conversion is quite efficient) there is not inherent size advantage compared to text. BLOB assumes that a byte is your atomic data unit, which is not true for Unicode you are denied access to essential text commands such as position, match regex, replace string, etc. but if things are working well, of course you don't need to convert them. ** 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 **
Re: unicode, blobs, and the web
> 2019/08/29 12:31、webmaster namethatplant.net > のメール: > > I still have a question. > The write-up for PROCESS HTML TAGS contains the warning, "It is now highly > inadvisable to store texts in BLOBs". > > I don't use the command "PROCESS HTML TAGS" but I have used BLOB variables in > several other places throughout my website. These don't contain any > troublemaker characters and they are working well. > > Do I need to convert them to text variables? storing text in BLOB is inadvisable for several reasons: BLOBs are not ref-counted and memory inefficient. there are copied when passed as a method argument, for example. BLOB to text conversion is costly, especially when the storage encoding is not UTF-8 (unicode to unicode conversion is quite efficient) there is not inherent size advantage compared to text. BLOB assumes that a byte is your atomic data unit, which is not true for Unicode you are denied access to essential text commands such as position, match regex, replace string, etc. but if things are working well, of course you don't need to convert them. ** 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 **
Re: Formulas with XLS Plugin
First I would fully recommend XL plugin from Pluggers, for any serious project. What I posted as "XLS" is a limited wrapper of xlslib (not libxls) http://xlslib.sourceforge.net the feature list (of the library) is here http://xlslib.sourceforge.net/features.php snd the TODO is here http://xlslib.sourceforge.net/todo.php I get it, there is not mention of formulae in either of them. there is a "SUM" function example in the sample DB. see also https://sourceforge.net/p/xlslib/discussion/402380/thread/63f60c1d/ the author discusses "translating Excel text formulas to internal formulas" but this is 2012. XLS is more or less deprecated in favour of XLSX, so I don't expect much to come for xlslib anyomre. ** 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 **
San Jose 4D training roommate?
Hi, Anyone going or sending an associate to the San Jose 4D training 9/30-10/4? I’d like to split the cost of a room for 5 days beginning 9/29. Respond soon so we can get the best rates. Thanks, Michael Ferguson ** 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 **
Re: Check Orphan Forms Warnings in MSC
Yah, success!! I overlooked that the orphans after the repair were located under _project_ forms not table forms! Then, every time I tried to select one I got into some endless loop where 4D refused to let me select the form as it was damaged. Eventually I managed it by holding down the Enter key. Once the form was open I deleted all objects from each of the 2 offending forms and was able to trash the form. The structure now verifies 100%!! Regards, Narinder Chandi, ToolBox Systems Ltd. -- -Original Message- From: 4D_Tech <4d_tech-boun...@lists.4d.com> on behalf of 4D Tech Mailing List <4d_tech@lists.4d.com> Reply-To: 4D Tech Mailing List <4d_tech@lists.4d.com> Date: Sunday, 1 September 2019 at 20:44 To: 4D Tech Mailing List <4d_tech@lists.4d.com> Cc: Narinder Chandi <4dtechmailingl...@toolbox.uk.com> Subject: Re: Check Orphan Forms Warnings in MSC ...and replying to my own previous message, now when I use "Find in Design" I get a dialog pop up twice with the message: "One field was bad. It has been suppressed from your form." Having this come up every time is going to be a PITA :(( Is there a way to fix this? Regards, Narinder Chandi, ToolBox Systems Ltd. -- -Original Message- From: 4D_Tech <4d_tech-boun...@lists.4d.com> on behalf of 4D Tech Mailing List <4d_tech@lists.4d.com> Reply-To: 4D Tech Mailing List <4d_tech@lists.4d.com> Date: Sunday, 1 September 2019 at 20:34 To: 4D Tech Mailing List <4d_tech@lists.4d.com> Cc: Narinder Chandi <4dtechmailingl...@toolbox.uk.com> Subject: Re: Check Orphan Forms Warnings in MSC Thanks Tim - I overlooked that! So, repairing the structure eliminated the previous FO4D warnings but I now have 9 new ones under Check Project Forms: ___Orphan___31086.Page1.Picture1 uses a deprecated picture format: PICT. ___Orphan___31086.Page1.Picture2 uses a deprecated picture format: PICT. ___Orphan___31086.Page1.Picture3 uses a deprecated picture format: PICT. ___Orphan___31086.Page1.Picture4 uses a deprecated picture format: PICT. ___Orphan___31086.Page1.Picture5 uses a deprecated picture format: PICT. ___Orphan___31086.Page1.Picture6 uses a deprecated picture format: PICT. ___Orphan___31086.Page1.Picture7 uses a deprecated picture format: PICT. ___Orphan___31086.Page1.Picture8 uses a deprecated picture format: PICT. ___Orphan___31086.Page1.Picture9 uses a deprecated picture format: PICT. Any ideas on how to find and/or remove these? Regards, Narinder Chandi, ToolBox Systems Ltd. -- -Original Message- From: 4D_Tech <4d_tech-boun...@lists.4d.com> on behalf of 4D Tech Mailing List <4d_tech@lists.4d.com> Reply-To: 4D Tech Mailing List <4d_tech@lists.4d.com> Date: Sunday, 1 September 2019 at 20:13 To: 4D Tech Mailing List <4d_tech@lists.4d.com> Cc: Tim Nevels Subject: Re: Check Orphan Forms Warnings in MSC On Sep 1, 2019, at 2:00 PM, Narinder Chandi wrote: > So, after a long, long hard slog migrating from v15 to v17, I have reduced the 6,000 MSC warnings down to the last 2. > > Under "Check Orphan Forms" I am seeing: > The form resource FO4D of id 31086 is not used anywhere > The form resource FO4D of id 21169 is not used anywhere > > How do I address these? I know probably I can just ignore them but it would be nice to have zero warnings! I have tried without success: > * compacting the structure > * delete the .4DIndy structure index file followed by compacting the structure > > Any other suggestions gratefully received! Did you do a “repair” of the structure? Not “compact”, but “repair”. Tim * Tim Nevels Innovative Solutions 785-749-3444 timnev...@mac.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 ** ** 4D Internet Users Group (4D iNUG) Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub
Re: Check Orphan Forms Warnings in MSC
...and replying to my own previous message, now when I use "Find in Design" I get a dialog pop up twice with the message: "One field was bad. It has been suppressed from your form." Having this come up every time is going to be a PITA :(( Is there a way to fix this? Regards, Narinder Chandi, ToolBox Systems Ltd. -- -Original Message- From: 4D_Tech <4d_tech-boun...@lists.4d.com> on behalf of 4D Tech Mailing List <4d_tech@lists.4d.com> Reply-To: 4D Tech Mailing List <4d_tech@lists.4d.com> Date: Sunday, 1 September 2019 at 20:34 To: 4D Tech Mailing List <4d_tech@lists.4d.com> Cc: Narinder Chandi <4dtechmailingl...@toolbox.uk.com> Subject: Re: Check Orphan Forms Warnings in MSC Thanks Tim - I overlooked that! So, repairing the structure eliminated the previous FO4D warnings but I now have 9 new ones under Check Project Forms: ___Orphan___31086.Page1.Picture1 uses a deprecated picture format: PICT. ___Orphan___31086.Page1.Picture2 uses a deprecated picture format: PICT. ___Orphan___31086.Page1.Picture3 uses a deprecated picture format: PICT. ___Orphan___31086.Page1.Picture4 uses a deprecated picture format: PICT. ___Orphan___31086.Page1.Picture5 uses a deprecated picture format: PICT. ___Orphan___31086.Page1.Picture6 uses a deprecated picture format: PICT. ___Orphan___31086.Page1.Picture7 uses a deprecated picture format: PICT. ___Orphan___31086.Page1.Picture8 uses a deprecated picture format: PICT. ___Orphan___31086.Page1.Picture9 uses a deprecated picture format: PICT. Any ideas on how to find and/or remove these? Regards, Narinder Chandi, ToolBox Systems Ltd. -- -Original Message- From: 4D_Tech <4d_tech-boun...@lists.4d.com> on behalf of 4D Tech Mailing List <4d_tech@lists.4d.com> Reply-To: 4D Tech Mailing List <4d_tech@lists.4d.com> Date: Sunday, 1 September 2019 at 20:13 To: 4D Tech Mailing List <4d_tech@lists.4d.com> Cc: Tim Nevels Subject: Re: Check Orphan Forms Warnings in MSC On Sep 1, 2019, at 2:00 PM, Narinder Chandi wrote: > So, after a long, long hard slog migrating from v15 to v17, I have reduced the 6,000 MSC warnings down to the last 2. > > Under "Check Orphan Forms" I am seeing: > The form resource FO4D of id 31086 is not used anywhere > The form resource FO4D of id 21169 is not used anywhere > > How do I address these? I know probably I can just ignore them but it would be nice to have zero warnings! I have tried without success: > * compacting the structure > * delete the .4DIndy structure index file followed by compacting the structure > > Any other suggestions gratefully received! Did you do a “repair” of the structure? Not “compact”, but “repair”. Tim * Tim Nevels Innovative Solutions 785-749-3444 timnev...@mac.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 ** ** 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 ** ** 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 **
Re: Check Orphan Forms Warnings in MSC
Thanks Tim - I overlooked that! So, repairing the structure eliminated the previous FO4D warnings but I now have 9 new ones under Check Project Forms: ___Orphan___31086.Page1.Picture1 uses a deprecated picture format: PICT. ___Orphan___31086.Page1.Picture2 uses a deprecated picture format: PICT. ___Orphan___31086.Page1.Picture3 uses a deprecated picture format: PICT. ___Orphan___31086.Page1.Picture4 uses a deprecated picture format: PICT. ___Orphan___31086.Page1.Picture5 uses a deprecated picture format: PICT. ___Orphan___31086.Page1.Picture6 uses a deprecated picture format: PICT. ___Orphan___31086.Page1.Picture7 uses a deprecated picture format: PICT. ___Orphan___31086.Page1.Picture8 uses a deprecated picture format: PICT. ___Orphan___31086.Page1.Picture9 uses a deprecated picture format: PICT. Any ideas on how to find and/or remove these? Regards, Narinder Chandi, ToolBox Systems Ltd. -- -Original Message- From: 4D_Tech <4d_tech-boun...@lists.4d.com> on behalf of 4D Tech Mailing List <4d_tech@lists.4d.com> Reply-To: 4D Tech Mailing List <4d_tech@lists.4d.com> Date: Sunday, 1 September 2019 at 20:13 To: 4D Tech Mailing List <4d_tech@lists.4d.com> Cc: Tim Nevels Subject: Re: Check Orphan Forms Warnings in MSC On Sep 1, 2019, at 2:00 PM, Narinder Chandi wrote: > So, after a long, long hard slog migrating from v15 to v17, I have reduced the 6,000 MSC warnings down to the last 2. > > Under "Check Orphan Forms" I am seeing: > The form resource FO4D of id 31086 is not used anywhere > The form resource FO4D of id 21169 is not used anywhere > > How do I address these? I know probably I can just ignore them but it would be nice to have zero warnings! I have tried without success: > * compacting the structure > * delete the .4DIndy structure index file followed by compacting the structure > > Any other suggestions gratefully received! Did you do a “repair” of the structure? Not “compact”, but “repair”. Tim * Tim Nevels Innovative Solutions 785-749-3444 timnev...@mac.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 ** ** 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 **
Re: Check Orphan Forms Warnings in MSC
On Sep 1, 2019, at 2:00 PM, Narinder Chandi wrote: > So, after a long, long hard slog migrating from v15 to v17, I have reduced > the 6,000 MSC warnings down to the last 2. > > Under "Check Orphan Forms" I am seeing: > The form resource FO4D of id 31086 is not used anywhere > The form resource FO4D of id 21169 is not used anywhere > > How do I address these? I know probably I can just ignore them but it would > be nice to have zero warnings! I have tried without success: > * compacting the structure > * delete the .4DIndy structure index file followed by compacting the structure > > Any other suggestions gratefully received! Did you do a “repair” of the structure? Not “compact”, but “repair”. Tim * Tim Nevels Innovative Solutions 785-749-3444 timnev...@mac.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 **
Check Orphan Forms Warnings in MSC
So, after a long, long hard slog migrating from v15 to v17, I have reduced the 6,000 MSC warnings down to the last 2. Under "Check Orphan Forms" I am seeing: The form resource FO4D of id 31086 is not used anywhere The form resource FO4D of id 21169 is not used anywhere How do I address these? I know probably I can just ignore them but it would be nice to have zero warnings! I have tried without success: * compacting the structure * delete the .4DIndy structure index file followed by compacting the structure Any other suggestions gratefully received! Regards, Narinder Chandi, ToolBox Systems Ltd. -- ** 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 **
Re: windows versions for 4D v13.6
You don’t. For a short period this customer is stuck using 4D v 13.6. It is that version I am asking about. Regards Chuck On Fri, Aug 30, 2019 at 10:35 PM JOHN BAUGHMAN via 4D_Tech < 4d_tech@lists.4d.com> wrote: > If I understand your question… > > Windows 10 - v17R5 64bit > Windows 2008 R2 Enterprise - v16 R6 64bit > > John > > > > On Aug 30, 2019, at 10:31 AM, Chuck Miller via 4D_Tech < > 4d_tech@lists.4d.com> wrote: > > > > Is anyone running server on OS newer than windows server 2003. If so > what version > > > > > > Regards > > > > Chuck > > > > > Chuck Miller Voice: (617) 739-0306 > > Informed Solutions, Inc. Fax: (617) 232-1064 > > mailto:cjmillerinformed-solutions.com > > Brookline, MA 02446 USA Registered 4D Developer > > Providers of 4D and Sybase connectivity > > http://www.informed-solutions.com > > > > > This message and any attached documents contain information which may be > confidential, subject to privilege or exempt from disclosure under > applicable law. These materials are intended only for the use of the > intended recipient. If you are not the intended recipient of this > transmission, you are hereby notified that any distribution, disclosure, > printing, copying, storage, modification or the taking of any action in > reliance upon this transmission is strictly prohibited. Delivery of this > message to any person other than the intended recipient shall not > compromise or waive such confidentiality, privilege or exemption from > disclosure as to this communication. > > > > ** > > 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 > > ** > > ** > 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 > ** -- - Chuck Miller Voice: (617) 739-0306 Fax: (617) 232-1064 Informed Solutions, Inc. Brookline, MA 02446 USA Registered 4D Developer Providers of 4D, Sybase & SQL Server connectivity https://www.informed-solutions.com - This message and any attached documents contain information which may be confidential, subject to privilege or exempt from disclosure under applicable law. These materials are intended only for the use of the intended recipient. If you are not the intended recipient of this transmission, you are hereby notified that any distribution, disclosure, printing, copying, storage, modification or the taking of any action in reliance upon this transmission is strictly prohibited. Delivery of this message to any person other than the intended recipient shall not compromise or waive such confidentiality, privilege or exemption from disclosure as to this communication. ** 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 **
