Thanks, but we do not generally going into production with r releases. Hard enough to get this client to upgrade as testing is so immense
Regards Chuck ------------------------------------------------------------------------------------------------ Chuck Miller Voice: (617) 739-0306 Informed Solutions, Inc. Fax: (617) 232-1064 mailto:cjmiller<AT SIGN>informed-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. > On Jan 17, 2017, at 9:16 PM, Wayne Stewart <[email protected]> wrote: > > Chuck, > > Cross table reports now in v16r2: > > http://blog.4d.com/4d-v16-r2-beta-test-starts-today/ > > Not certain if you're on the leading or the bleeding edge though. > > > Regards, > > Wayne > > > Wayne Stewart > about.me/waynestewart > > > > > On 18 January 2017 at 12:40, Chuck Miller > <[email protected]> wrote: >> HI Tim, >> >> Thanks for response. No clients killall be 32 bit. We can not move to total >> 64 bit since as far as I know quick report (64) doe snot have cross table >> reports, which we use and we have too much code in 4d write to move to pro. >> Testing would be too much at this point >> >> Regards >> >> Chuck >> ------------------------------------------------------------------------------------------------ >> Chuck Miller Voice: (617) 739-0306 >> Informed Solutions, Inc. Fax: (617) 232-1064 >> mailto:cjmiller<AT SIGN>informed-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. >> >>> On Jan 17, 2017, at 7:52 PM, Timothy Penner <[email protected]> wrote: >>> >>> >>> You plan to use 4D Server 64 bit to take advantage of more ram; makes >>> perfect sense... but your curious if there is anything you need to know >>> about 4D Write before switching to use 4D Server 64 bit (I assume this is >>> for Mac since 4D Server 64 bit has been available for Windows since v12)? >>> >>> I can only think of the following restrictions: >>> * 4D Write cannot run on 4D Server 64 bit for Mac, so don’t execute the >>> commands on the server. >>> * There is no problem using 4D Write on 32 bit Clients that are connected >>> to a 64 bit Server, you just can't execute the commands on the Server >>> >>> Since it is just the 4D Server you are changing from 32 bit to 64 bit, then >>> there isn't really anything else about 4D Write to be made aware of... >>> Nothing else in regards to 4D Write is really affected when changing from >>> 4D Server32 bit to 4D Server 64 bit. >>> >>> On the other hand, if you plan to swap to 64 bit Clients also, then you >>> will need to handle the conversion of the 4D Write documents and 4D Write >>> Areas prior to switching (as 4D Write is unavailable with 64 bit Client). >> >> ********************************************************************** >> 4D Internet Users Group (4D iNUG) >> FAQ: http://lists.4d.com/faqnug.html >> Archive: http://lists.4d.com/archives.html >> Options: http://lists.4d.com/mailman/options/4d_tech >> Unsub: mailto:[email protected] >> ********************************************************************** > ********************************************************************** > 4D Internet Users Group (4D iNUG) > FAQ: http://lists.4d.com/faqnug.html > Archive: http://lists.4d.com/archives.html > Options: http://lists.4d.com/mailman/options/4d_tech > Unsub: mailto:[email protected] > ********************************************************************** ********************************************************************** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: http://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
