Stephen, It depends on how much stuff you are storing in your forms. An uncompressed form that has a lot of things going on in it (Eeps, custom code, etc.) still has to move across a network. If you have a fast network it may not be a noticeable difference.
The advantage to compression is that they move across the network faster. The disadvantage is that they become harder to search from a SYS level. Jan -----Original Message----- From: "Stephen Markson" <[email protected]> To: [email protected] (RBASE-L Mailing List) Date: Mon, 6 Apr 2009 15:14:19 -0400 Subject: [RBASE-L] - Re: Custom eeps Thank you all again. I’ve got this mostly figured out now. It appears the forms in this DB are stored uncompressed, but compression is set on. It could be a different setting here and at the client site. What is the default? What are the advantages/disadvantages to form compression? Regards, Stephen Markson ForenSys The Forensic Systems Group www.ForenSys.ca 416 512 6950 From: [email protected] [mailto:[email protected]] On Behalf Of Lawrence Lustig Sent: April 6, 2009 2:18 PM To: RBASE-L Mailing List Subject: [RBASE-L] - Re: Custom eeps << Thanks for your replies. I am aware of the "document eeps" feature, but is there a query that can determine which forms in a DB contain custom eeps? >> If you have forms compression set on then the forms are stored in a binary format, and there isn't really any way to recognize whether they have EEPs or not. If they're stored without compression, you could try to write a query that would do a CONTAINS search on the form data column, looking for R:Base's internal name for the EEP inside the data. -- Larry
