Atticus,

I'm largely in agreement with what you've said. Also, I'm glad that the code snippet helped. I've got more if you have any questions. In any case, I think we're all pretty much in agreement that this is an area that is key to our particular area.

quote:

Originally posted by Atticus:

So are you using DL on a network? Is it fairly snappy?

I normally use DL Offline right now, but that's primarily because my main server (an XServe) is not at my office. I sync every day and so does my law partner. I plan to move to an online configuration shortly for the law firm and I'll let you know how that goes. However, I can tell you that I use DL for another business and we even have users that use DL over the internet (DSL connections on both ends) and find it very usable.

In short, I guess I'm somewhat surprised that you're concerned with DL's performance. Of all of the comments I hear about DL, performance doesn't seem to bee an issue for most users, even with a large number of records. I take it that Time Matters must have some performance issues...

In my experience, DL is very dependent on the performance of the server that it is on. On my Dual processor 1.33 Ghz XServe (2 Gig RAM), performance is excellent on my MacBook, even over wireless. I have a feeling that any current XServe (or MacPro) would be able to handle just about any DL configuration that you could throw at it. Of course, if you're really interested, I'm sure there would be someone better suited to speak to that aspect than myself.

quote:

I guess I'm somewhat surprised that you're concerned with DL's performance. Of all of the comments I hear about DL, performance doesn't seem to bee an issue for most users, even with a large number of records. I take it that Time Matters must have some performance issues...

It's just that TM is so slow over our network. I have read the occasional post about DL slowing down, but nothing alarming. I'm hoping to get my hands on a Time Capsule soon for home use and hook up a few Macbooks via ethernet to give it a test. Of course, I won't have near the amount of data I have in TM to play with, but it'll be a start.

One other thing. I did try out my watermark idea with Word 2008. Merge keys in text boxes don't work. Merge keys in tables do. (Table for one!) So that made me happy!

Cheers, George. Thanks again for your help.

Hello,

Here is a KB article that lists all the merge keys for using with letter templates.

http://www.marketcircle.com/kb/idx/0/527/article/

Hope you find this useful.

Thanks

quote:

Originally posted by Shailaja:
Hello,

Here is a KB article that lists all the merge keys for using with letter templates.

http://www.marketcircle.com/kb/idx/0/527/article/

Hope you find this useful.

Thanks

I just wanted to follow up on this one and clarify something. That document does list the merge keys for EXTERNALLY MERGED templates. It is not by any means complete if you're using the internal merge engine, as evidenced by the code snippet that I posted earlier. If you want the entire list of merge keys, the document you're looking for is called Daylite Data Description and it is in the Daylite Developer Kit. I'm not sure why Shailaja didn't make that clear...

Hi George,

This document was initially aimed at beginners or average Daylite users. However, now we have added a link to the Daylite Developer kit in this document, so that advanced users find it useful too.

Thanks.

quote:

Originally posted by Shailaja:
Hi George,

This document was initially aimed at beginners or average Daylite users. However, now we have added a link to the Daylite Developer kit in this document, so that advanced users find it useful too.

Thanks.

Shailaja,

I think that will be helpful to some. I know that the developer docs can be hard to find (I actually had to email my brother the PDF just this past weekend because the only thing he could find on this forum were my posts referencing the developer docs).

quote:

Originally posted by Atticus:
[QUOTE]
One other thing. I did try out my watermark idea with Word 2008. Merge keys in text boxes don't work. Merge keys in tables do. (Table for one!) So that made me happy!

Thank you so much for researching this! I am having problems getting the table cells to line up on top of the watermark. As I draw new cells, they all seem to be linked together and when I try to move one, (which seems very difficult to move slightly even with gridlines unchecked), adjoining cells move at the same time.

I tried the "split cells" command to no avail.

Thanks again,

Jay

I noticed the same thing but thought it was because I had type some text over the bookmark, then added some cells. But I didn't have time to go any further with it. Just seems like a bug in Word.

quote:

Originally posted by Atticus:
I noticed the same thing but thought it was because I had type some text over the bookmark, then added some cells. But I didn't have time to go any further with it. Just seems like a bug in Word.

This gets back to the discussion of internal or external editors, but I found that by bringing in a PDF image of the form into the "Print Layout" editor I can create great dynamic and static text boxes to fill in the form information.

One last problem to solve is that I would like to create a form associated with a contact and then merge that data into the Print Layout or Report. I know how to merge form data with a letter template, but does anyone know if form data can be merged into a report or print layout?

Thanks - Jay

quote:

Originally posted by George Qualley:

quote:

Originally posted by Shailaja:
Hello,

Here is a KB article that lists all the merge keys for using with letter templates.

http://www.marketcircle.com/kb/idx/0/527/article/

Hope you find this useful.

Thanks

I just wanted to follow up on this one and clarify something. That document does list the merge keys for EXTERNALLY MERGED templates. It is not by any means complete if you're using the internal merge engine, as evidenced by the code snippet that I posted earlier. If you want the entire list of merge keys, the document you're looking for is called Daylite Data Description and it is in the Daylite Developer Kit. I'm not sure why Shailaja didn't make that clear...

Me again... Confused again. George, can you tell me what you mean be 'externally merged templates'. My understanding was there are two types of merge - internal and external, the former done with the internal DL text editor (to which it appears the above cited merge keys apply) and the external merge function which allows you to merge to templates created in Word, Excel, etc. Please explain.

cheers,

quote:

Originally posted by Tim Jacka:

Me again... Confused again. George, can you tell me what you mean be 'externally merged templates'. My understanding was there are two types of merge - internal and external, the former done with the internal DL text editor (to which it appears the above cited merge keys apply) and the external merge function which allows you to merge to templates created in Word, Excel, etc. Please explain.

Tim,

I don't think that you're confused (at least not according to your description). It's entirely possible that it's my terminology. After all, I just made up the Internal/External distinction for convenience sake. To be sure, there's some different technology at work, but I could easily be referring to things incorrectly...

Today, I found out that there are merge keys for Projects and Opportunities, which worked well on Word 2008 and the built-in Daylite editor (as expected) after testing. Very exciting.

However, merge keys for Projects and Opportunities, such as <$project.name$> or <$project.extra1$>, do not work for me in Excel 2008 and 2004, but do work in Numbers. I need to use Excel and would like to merge Project fields (name, dates, extra fields, etc) into an Excel .XLS file.

I tried this with two different computers, with no luck. Can someone shed light on this problem? Is it just not possible (for now)?

Thank you.

Are you choosing from the official set of merge keys for Excel:
External Merge Keys Guide

Mat,

If by official set of merge keys for Excel, you mean keys such as

<$project.name$> 
<$project.modifyDate$>  
<$project.assignedTo.contact.name$>
<$project.extra1$>  
<$project.extra2$>  
etc.

yes, those are the kinds of keys that are not working in Excel 2004/2008.

Just following-up on the project merge key problem with Excel. Am I the only one with the problem above?

Merge keys for projects seem to work in Numbers (although numbers are treated as text), but not in Excel.

Any help would be greatly appreciated. Thank you.