it is all in the stars David :)
>
> Does anyone know, is there an actual 'vote' mechanism, or are you just
> supposed to put down a +1 post?
Hell is other people
Jean-Paul Sartre
**
4D Internet Users Group
I've been making a more concerted effort to write test code as part of new
modules and was doing pretty well. Then I started working on something and
The Fever took hold - I just kept grinding out code. After a couple of
weeks, I realized I could do a really, really big improvement with a
rewrite.
Here's one of those thoughts that I think to repost every few years.
Many of us use variable naming conventions to carry various bits of
information about what's in the variable/array. Like this format:
vtCity
vlWindow
Of course, no one uses that particular format as it's use will later
condemn
for investigative purposes, and brute-force correction,
you could peek the structure/data UUID using this tool
https://github.com/miyako/4d-utility-uuid-manager
UUID replaces the old WEDD resource.
> 2017/02/24 0:53、bob.miller--- via 4D_Tech <4d_tech@lists.4d.com> のメール:
> This is in v15r4, and
> Le 23 févr. 2017 à 18:17, Cannon Smith via 4D_Tech <4d_tech@lists.4d.com> a
> écrit :
>
> Hi Arnaud,
>
> You are right, the code does not handle case sensitivity for property names
> correctly. [...]
now it's perfect to be stolen ;-)
Many thanks!
--
Arnaud de Montard
If the field is set as an Alpha field then you could activate the "Auto UUID"
option with this code:
Begin SQL
ALTER TABLE Table_1 MODIFY uidField ENABLE AUTO_GENERATE;
End SQL
You could also set that field to the primary key using this code:
Begin SQL
ALTER TABLE Table_1 ADD PRIMARY
I created, in v12 a number a field in a number of tables ' journal_key'
which was/is to be the UUID field for journaling. It was/has never been
populated.
When I created the field in v12 I did not want to fight with the UUID
issues present.
Now, in v13 I am looking to implement this
I don’t think visibility can be set at all via SQL, for new or existing fields:
http://doc.4d.com/4Dv15/4D/15/CREATE-TABLE.300-2288142.en.html
http://doc.4d.com/4Dv15/4D/15/ALTER-TABLE.300-2288140.en.html
http://doc.4d.com/4Dv15/4D/15/System-Tables.300-2288116.en.html
-Tim
How about on windows zip the entire folder and on mac zip the application.
The write a script to unzip and put in the correct place
Regards
Chuck
On Wed, Feb 22, 2017 at 4:16 PM, Justin Leavens via 4D_Tech <
4d_tech@lists.4d.com> wrote:
> I have a customer site with a mix of Windows machines
Hi Arnaud,
> On Feb 22, 2017, at 2:25 PM, Arnaud de Montard via 4D_Tech
> <4d_tech@lists.4d.com> wrote:
>
>> : ($atFirstProperty{$x}#$atSecondProperty{$x}) //Check property name
>
> About the comparison above, json properties are case sensitive.
> Things like:
>
Hi Everyone,
During a recent upgrade where I created a compiled/merged app with 4D
Server, when I deploy the new compiled/merged app I get this message:
The structure and data fiels to not correspond to each other. The data
file cannot be opened with the structure.
This is in v15r4, and I
David
This slightly changes the topic of the OLD on Object fields to a more detailed
discussion of the ‘shortcomings' of objects….
(On the topic of the former in my case if I am creating an object in code its
likely to be created with the same key order each time so if the ’stringified'
Two remarks to the Windows crash dump:
- If the app is running in a by Windows write protected folder the crash dump
is saved in the so called virtual store, e.g. if the 4D.exe of 4D V15.3 is
crashed you will find the dump under
"C:\Users\\AppData\Local\VirtualStore\Program Files (x86)\4D\4D
13 matches
Mail list logo