RE: Storage + New shared object
Hi David,
First Both, $DeleteRecord_ob and $DeleteRecord_PN_ob must be a shared objects.
Also, it seems that shared objects do not accept arrays. Convert the arrays to
shared collections instead.
This should work:
ARRAY TEXT($DeleteRecord;Get last table number)
ARRAY LONGINT($DeleteRecord_PN;Get last table number)
C_COLLECTION($t)
$t:=New shared collection
ARRAY TO
COLLECTION($t;$DeleteRecord;"DeleteRecord";$DeleteRecord_PN;"DeleteRecord_PN")
Use (Storage)
Storage.t:=$t
End use
Lahav
-Original Message-
From: 4D_Tech <4d_tech-boun...@lists.4d.com> On Behalf Of David Ringsmuth via
4D_Tech
Sent: Saturday, September 1, 2018 9:36 PM
To: 4D iNug Technical <4d_tech@lists.4d.com>
Cc: David Ringsmuth
Subject: Storage + New shared object
I’m trying to add an object array to Storage.
The documentation says that Objects can be a share storage value.
I keep getting the message “Not supported value type in a shared object or
shared collection.”
In the below code I broke apart the assignments for easiest debugging.
ARRAY TEXT($DeleteRecord;Get last table number) ARRAY
LONGINT($DeleteRecord_PN;Get last table number)
C_OBJECT($DeleteRecord_ob)
OB SET ARRAY($DeleteRecord_ob;"DeleteRecord";$DeleteRecord)
C_OBJECT($DeleteRecord_PN_ob)
OB SET ARRAY($DeleteRecord_PN_ob;"DeleteRecord_PN";$DeleteRecord_PN)
C_OBJECT($Delete_ob;$Delete_PN_ob)
Use (Storage)
Storage.t:=New shared
object("DeleteRecord";$Delete_ob;"DeleteRecord_PN";$Delete_PN_ob)
End use
Use (Storage.t)
Storage.t.DeleteRecord:=$DeleteRecord_ob // this line generated the
error message
Storage.t.DeleteRecord_PN:=$DeleteRecord _PN_ob// so does this line
error with same message End use
Please help!
David Ringsmuth
**
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
**
Storage + New shared object
I’m trying to add an object array to Storage.
The documentation says that Objects can be a share storage value.
I keep getting the message “Not supported value type in a shared object or
shared collection.”
In the below code I broke apart the assignments for easiest debugging.
ARRAY TEXT($DeleteRecord;Get last table number)
ARRAY LONGINT($DeleteRecord_PN;Get last table number)
C_OBJECT($DeleteRecord_ob)
OB SET ARRAY($DeleteRecord_ob;"DeleteRecord";$DeleteRecord)
C_OBJECT($DeleteRecord_PN_ob)
OB SET ARRAY($DeleteRecord_PN_ob;"DeleteRecord_PN";$DeleteRecord_PN)
C_OBJECT($Delete_ob;$Delete_PN_ob)
Use (Storage)
Storage.t:=New shared
object("DeleteRecord";$Delete_ob;"DeleteRecord_PN";$Delete_PN_ob)
End use
Use (Storage.t)
Storage.t.DeleteRecord:=$DeleteRecord_ob // this line generated the
error message
Storage.t.DeleteRecord_PN:=$DeleteRecord _PN_ob// so does this line
error with same message
End use
Please help!
David Ringsmuth
**
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
**
Sending multipart emails to Yahoo
When we send multipart emails to Yahoo addresses, they either bounce or simply disappear into the universe. When they bounce, they have an error Remote host said: 554 Message not allowed - [299] Looking up that error message isn't very helpful; "You'll receive an SMTP error or failed delivery message that includes "554 Message not allowed" when the content of a message you're trying to send violates Yahoo Mail policies. Content that violates policies includes; objectionable links, malicious attachments, or bad header information." I'm pretty sure the emails don't contain any objectionable links and certainly no malicious attachments (or any attachments at all), so perhaps there's something it doesn't like about the headers. But how to figure that out? Has anybody run into this, and were you able to resolve it? Pat -- * CatBase - Top Dog in Data Publishing tel: +44 (0) 207 118 7889 w: http://www.catbase.com skype: pat.bensky * ** 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: Isolating the Cause of a Server Crash
On Sep 1, 2018, at 2:00 PM, Dave Nasralla wrote: > One of our systems is crashing about every 3 days and I can't seem to > isolate the cause. Lately these are crashes with a Mac crash report > appearing on the screen. > Some system details are: > - 4D Built Server app with v17.0 HF1 (64 bit Server with 64 Mac and > 32 bit Windows Clients) > - Mac and Windows Clients > - Mac OS 10.13.5 > > What I know so far: > - I have the Server Debug file. It ends with a "." and so the last > command appears to have executed. > - I'm using the Report Info component, logging every 5 minutes. There > doesn't seem to be memory problems or run away cache issues. > - I also know who was one each time it crashes and said out an email > to those users to find patterns (so far I've found none). > - The crashes typically happen around 10am to 11am. > - The client and server builds match. > > I'm debating turning on the client debugger files and then harvesting > them afterwards when the user logs back in. I'm open to other > debugging techniques. > > There are other v17 systems running on the same machine with zero issue. > > Below is a snippet of the crash report. It seems to be different each > time, but here is the latest. Thread 73 crashed, so I only included > that one. > > Thanks, > > dave nasralla > > Process: Corporate [93958] > Path: /Users/USER/*/Corporate > Server.app/Contents/MacOS/Corporate > Identifier:4d.com.Corporate Server.app > Version: 17.0 build 17.226566 (???) > Code Type: X86-64 (Native) > Parent Process:??? [1] > Responsible: Corporate [93958] > User ID: 501 > > Date/Time: 2018-08-31 11:00:05.952 -0500 > OS Version:Mac OS X 10.13.5 (17F77) > Report Version:12 > Anonymous UUID:723511FD-4CA0-6E8B-0642-883209248DFC > > > Time Awake Since Boot: 370 seconds > > System Integrity Protection: enabled > > Crashed Thread:73 LabProjects List (id = -114) > > Exception Type:EXC_BAD_ACCESS (SIGSEGV) > Exception Codes: EXC_I386_GPFLT > Exception Note:EXC_CORPSE_NOTIFY > > Termination Signal:Segmentation fault: 11 > Termination Reason:Namespace SIGNAL, Code 0xb > Terminating Process: exc handler [0] > -- > > > Thread 73 Crashed:: LabProjects List (id = -114) > 0 4d.com.Corporate Server.app 0x00010694fdbe > V4DConnection::OnPostpone(bool) + 40 > 1 4d.com.Corporate Server.app 0x000106b095f7 > V4DServerUser::PostponeServiceConnection() + 35 > 2 4d.com.Corporate Server.app 0x000106b20567 > V4DServer::exec_ConnectionPostpone(V4DRequestReply&, V4DTaskConcrete*, > short) + 395 > 3 4d.com.Corporate Server.app 0x000106b211ca > V4DServer::exec_streamreq(V4DRequestReply&, V4DTaskConcrete*) + 100 Hi Dave, Crashing every 3 days is a real problem and totally unacceptable. So what can be done to try and make this situation better? We need to make changes to make this crashing stop. But what changes? Here is my thinking as I read this crash report. Keep in mind I’m not an expert on this, so I may be wrong in some areas. If I am wrong hopefully those that know more can correct me — and in turn help me and others understand more about how to read these macOS crash reports. (Thinking about Miyako, JPR, Christian Sakowski and Rob Laveaux — they are real experts in this area. Real macOS programmers that know how to read these things properly.) The crash report is supposed to provide a programmer with information on exactly here the program crashed and the cause of the crash. If you have the special 4D “debug” version it will contain more “symbols” and thus when 4D crashes you get better names for functions instead of just memory address offset. I think you even get 4D command names that were involved in the crash. But the basic crash dump info that we have here can help point to the general area of concern. Here is a website that helps explain crash dumps and how to read them: https://www.maketecheasier.com/read-macos-crash-reports-troubleshoot-mac/ This is 4D v17.0 build 226566 that is running compiled in 64bit mode (Code Type: x86-64). So first thought is that this could be a 4D 64bit issue. That’s important because some of the code is completely different between 32bit 4D and 64bit 4D. The 64bit code could be newly written code, the 32bit code could be legacy code that has been around for years. Thread 73 “LabProjects List” is what crashed. Do you have a table named “LabProjects” or maybe a MODIFY SELECTION or a listbox window that shows records in this table? Or a process that has that name? Makes me think that you do. That’s another pointer to where in your application the crashing problem occurred. Exception Type is "EXC_BAD_ACCESS (SIGSEGV)” and that means "the progra
Application menu bar.
v16.3 I'm building my menus by using INSERT MENU ITEM, APPEND MENU ITEM and SET MENU BAR. I am not always using a File menu and I would like to enable/disable the Quit menu item in the application menu bar. How do I do that with enable/disable menu item? -- Jim Dorrance jim.dorra...@gmail.com 4...@dorrance.eu www.4d.dorrance.eu PS: If you know of anyone that needs an experienced 4D programmer to add energy and experience to their team, please let me know. I have experience in many areas. Reasonable rates. Remote or Paris only. ** 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 **
