Re: About using the Hidden Rows Array on listboxes

v14 introduced LISTBOX SET ARRAY & LISTBOX Get array but I think in v13 you are limited to using process arrays. http://doc.4d.com/4Dv15R5/4D/15-R5/LISTBOX-SET-ARRAY.301-2937057.en.html http://doc.4d.com/4Dv15R5/4D/15-R5/LISTBOX-Get-array.301-2937056.en.html > 2016/12/10 7:29、Kirk Brooks

RE: 4D v14 Quick Report formatting of time fields

Hi Gary, I tested it and it appears to be working fine in v15.3. Best Regards, -Tai B. ** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options:

Re: Query editor in v15

Guy, I’ve seen even the v12 searches do not work perfectly. Sometimes the comparison values don’t make it. I’ve had a crash while loading a two field query which I had just saved from v12. Paul > Le 9 déc. 2016 à 22:54, Guy Algot a écrit : > > Paul, watch out for searches

Re: Query editor in v15

Guy, ​That's a good point.​ On Fri, Dec 9, 2016 at 1:52 PM, Guy Algot wrote: > Whatever you want to call it, I think Lee’s comment is spot on. Have you > seen how many ‘features’ get voted for in the forum but we get a new editor… > -- Kirk Brooks San Francisco, CA

About using the Hidden Rows Array on listboxes

I have always used this with a process array. But I'm wondering how or if I can use it with a dynamic array also. So the question is if I have a listbox populated with dynamic columns (you know, just an object name and 4D is managing the variable) how do I use the Hidden Rows Array in a similar

Re: v13.5/6 on OSX 10.11 el capitan

4D v13.6 crashes quite a bit in macOS 10.11.x, especially when switching apps. It might be usable if the users open 4D and do not ever switch to another application. 4D 13.6 was stable on macOS 10.10.x. I haven’t tried 15.3 on 10.10.x so I can’t advise you there. Jim Crate > On Dec 9, 2016,

Re: Query editor in v15

HI Miyako, > it could be optimised by some caching mechanism I guess... > I could work on it if you really need it. I second Paul’s request! And who told you that it was not needed outside of Japan? My client absolutely HATES the new query editor. Thank you for creating this component

Query editor in v15

Oh my, I just discovered the new query editor in v15. We let our users have access to the standard 4D query editor. The one in v14/v15 is radically different and I find it quite hard to use. Having to use drop-down menus is quite cumbersome in tables with lots of fields.

Re: Query editor in v15

Hi Paul, If you like to hang on the old behavior, Keisuke has written a component for that purpose. https://github.com/miyako/4d-component-classic-query-editor Haven't tested myself, though. In my projects I usually create a limited more user friendly query window to allow normal users perform

Re: Query editor in v15

We have always have the first two checked. However, not the third involving SQL joins. I’ll check that one too and try again. Thanks, Paul > Le 09 Dec 2016 à 12:35, Thomas Maul a écrit : > >> Query([Invoices];[Clients]City=“Los Angeles”) in the query editor >> will be

Re: Query editor in v15

the editor follows all relations from all fields for any depth, not just "1" relations as in the classic editor, but also "n" relations too, since QUERY is optimised for n fields since v11. it could be optimised by some caching mechanism I guess... I could work on it if you really need it. (I was

RE: Query editor in v15

> Query([Invoices];[Clients]City=“Los Angeles”) in the query editor > will be run sequentially, even if there’s an automatic relation between the > two tables and even > if City is indexed. If you have hundreds of thousands, or millions of > records, this is a killer. Your structure is from

Re: Query editor in v15

Thomas, Yes, it was the SQL Joins which made the difference. Things ran fine in v11, v12 and v13 but the new query editor in v14/v15 really requires this option in order to run correctly. Thanks, Paul > Le 09 Dec 2016 à 12:35, Thomas Maul a écrit : > >>

Re: Query editor in v15

Maybe Miyako will have a fix for that. I’m assuming it’s the complexity of the structure but I may be wrong. Paul > Le 09 Dec 2016 à 13:06, Alan Chan a écrit : > > Aruh we have 204 tables:-( > > Alan Chan > > 4D iNug Technical <4d_tech@lists.4d.com> writes: >> Miyako

Re: Query editor in v15

Hi Miyako, It would be a very useful feature for us to have such a tool. I especially like the way you handle the one-to-many relationships. It’s much clearer than the old query editor, not to mention the new one in v14/v15 which I find akward. What would that entail for you and for us?

Re: Query editor in v15

Hi Paul, Please let us know how it works. I love its localization. Thanks to another great work from Miyako that ease migration to v15. Alan Chan 4D iNug Technical <4d_tech@lists.4d.com> writes: >Thanks, > >I’ll look at that! > > >Paul > > >> Le 9 déc. 2016 à 12:03, Keisuke Miyako

Re: Query editor in v15

Miyako has done a great job here. However, it takes about 10 seconds for the dialog to open. I suppose it’s because we have about 220 tables and it’s taking the time to analyse the structure. The results of the queries seem very well optimized. Paul > Le 09 Dec 2016 à 12:18, Alan Chan

Re: Query editor in v15

Aruh we have 204 tables:-( Alan Chan 4D iNug Technical <4d_tech@lists.4d.com> writes: >Miyako has done a great job here. > >However, it takes about 10 seconds for the dialog to open. I suppose it’s >because we have about 220 tables and it’s taking the time to analyse the >structure. >

Re: slightly off

> I have a small customer that has no in house IT staff. They use another > consultant for OS related stuff. There are an all mac shop, which currently > has an internal drive mounted for all that has documents on it. They want > to move to BOX and have all in the cloud. What are others doing re

Re: Query editor in v15

if you prefer classic: https://github.com/miyako/4d-component-classic-query-editor > 2016/12/09 19:02、Paul Lovejoy のメール： > We let our users have access to the standard 4D query editor. The one in > v14/v15 is radically different and I find it quite hard to use. 宮古

Re: Query editor in v15

Thanks, I’ll look at that! Paul > Le 9 déc. 2016 à 12:03, Keisuke Miyako a écrit : > > if you prefer classic: > > https://github.com/miyako/4d-component-classic-query-editor > >> 2016/12/09 19:02、Paul Lovejoy のメール： >> We let our users have

RE: Query editor in v15

Alan, You may prefer to use BB_Find. Great detail find editor, saved queries, fast, typing-finder for fields, etc… Contact tonyring at bbsp dot com David Ringsmuth From: Alan Chan Sent: Friday, December 9, 2016 6:06 AM To: 4d_tech@lists.4d.com Subject: Re: Query editor in v15 Aruh we

Re: Query editor in v15

Hi David, Thanks for the tips. Does BB_find have same interface like the old Query Editor? Many customers have been using the query editor for more than 20 years and get so used to it. They are conservative and hate anything different that require learning unless it's new function (not existed

Re: Query editor in v15

On Fri, Dec 9, 2016 at 2:02 AM, Paul Lovejoy wrote: > > Does anyone else let your users access the standard editor? If so, how > have you dealt with the transition from v12/v13 queries to v14/v15, or am I > alone? I just apologize and say it's not my fault. The change

Re: v13.5/6 on OSX 10.11 el capitan

I have one client on 13 who I'm sure is running El Capitan. I develop on it (rarely) and I'm still on El Capitan. On Fri, Dec 9, 2016 at 10:15 AM, wrote: > Tim, > > Thanks! > > I have the cert matrixes for both v13.5/6 and v15.3. > > But I wanted to know if someone was

RE: Query editor in v15 - Specified Module Not Found

Miyako, Many, many thanks for this! However, Upon starting my DB, I get: "The specified module could not be found" Got any ideas about this? Thanks Randy Engle XC2 Software LLC ** 4D Internet Users Group (4D iNUG) FAQ:

Re: Query editor in v15

Agreed! (Chart is another story) > Le 9 déc. 2016 à 15:36, Alan Chan a écrit : > > You are definitely misinformed. Any help in Query Editor and Chart would be > greatly helpful for migration to v15. > > Alan Chan > > 4D iNug Technical <4d_tech@lists.4d.com> writes: >> it

v13.5/6 on OSX 10.11 el capitan

Please let me know if you are running 4D v13.5/6 on OSX 10.11. I’m seeking a transition OSX that will run both 13.5/6 and v15.2. In the 13.5/6 db we have plugins NTK (2.0.6), Active4D (6.0r11), and 4DIC plugins (6.0 build 15.0) Thanks! David Ringsmuth

RE: v13.5/6 on OSX 10.11 el capitan

Hi David, > I’m seeking a transition OSX that will run both 13.5/6 and v15.2. Look at the Certification Matrix for both v13.6 and v15.3... v15.3: http://download.4d.com/Documents/Products_Documentation/LastVersions/Line_15/VIntl/20161104_CertifV15_3_INTL.pdf v13.6:

RE: v13.5/6 on OSX 10.11 el capitan

Tim, Thanks! I have the cert matrixes for both v13.5/6 and v15.3. But I wanted to know if someone was RUNNING v13.5/6 on OSX 10.11 or 10.12, with 3 plugins.  David Ringsmuth From: Timothy Penner Sent: Friday, December 9, 2016 11:40 AM To: 4D iNug Technical Subject: RE: v13.5/6 on OSX 10.11

Re: Query editor in v15

Lee, ​I'll be contrarian and suggest the itch is 'modernity'. The old query editor is really confusing to people coming to it for the first time. ​Which, if I look around the room, is none of us. Rolling that out to new users is sort of like calling your IT guy into the room and he looks like he

4D v14 Quick Report formatting of time fields

When I set the format of a time field in the v14 QR editor, it always displays/prints as military time rather than the format that I try to set (HH:MM AM/PM). Is this a known bug in v14? If so, has it been fixed in v15? ** 4D

Re: Query editor in v15

I figure it was considered an aesthetic improvement. Maybe they could have called it Query Pro and it could then co-exist with the old one for a while. :-) (and it’s fairly low on my list, I’m only commenting because it came up…) > On Dec 9, 2016, at 11:44 AM, Kirk Brooks

Re: Query editor in v15

Interesting. Most IT folks like the old query editor when we showed it the first time. Also, most mid managers found it easy to understand and use even they don't have IT knowledge. Alan Chan 4D iNug Technical <4d_tech@lists.4d.com> writes: >The old query editor is really confusing to people

Re: Query editor in v15

Nicely stated Kirk! Thanks, Robert > On Dec 9, 2016, at 1:44 PM, Kirk Brooks wrote: > > Lee, > > ​I'll be contrarian and suggest the itch is 'modernity'. > > The old query editor is really confusing to people coming to it for the > first time. ​Which, if I look around

Re: Query editor in v15

Whatever you want to call it, I think Lee’s comment is spot on. Have you seen how many ‘features’ get voted for in the forum but we get a new editor… > On Dec 9, 2016, at 12:44 PM, Kirk Brooks wrote: > > ​I'll be contrarian and suggest the itch is 'modernity'. > > On

Re: Query editor in v15

Paul, watch out for searches saved from the editor in a version previous to v12 and brought forward... > On Dec 9, 2016, at 3:02 AM, Paul Lovejoy wrote: > > Oh my, > > I just discovered the new query editor in v15. > > We let our users have access to the standard

Re: Query editor in v15

Luckily they didn’t get to the sort editor or the QR editor. > Le 9 déc. 2016 à 19:50, Lee Hinde a écrit : > > > I just apologize and say it's not my fault. The change seemed gratuitous. > I.e., I'm not clear what itch got scratched with that change.