Is there a limit on the number of items that can be in the list? I was using this list to do a lookup on a company and then the employees associated with that company. When I have a small number of companies it works fine but when I go over about 100 the
duplicates do not get removed from the list. Below is the code I have added.

SPCascadeDropdowns is going to grab the full set of values from the Contacts list every time. If you want to remove duplicates on each change, then I think you are going to need to use the completefunc on the SPCascadeDropdowns function. Check
the documentation on this and post back if you have more questions.

I am as we say sometimes LCD (lowest common .....) and I finally got the cascade function to work. Is there any way you can post a step by step guide to using the complete function to elminate duplicates. I am using a simlar setup to your examples where
"State" is the Parent column and of course I have duplicates. Any help is greatly appreciated.

Marc is on vacation, but I'll see if I can help you with this. If you define a function for compeltefunc, it fires automatically anytime the SPCascadeDropdowns function finishes processing. You can either reference a function that you define seperately,
or you can build the function right inside the SPCascadeDropdowns call, though I tend to call a seperate function as it's easier for me to follow my code that way (so that's how this example works).

I tested this on a stand-alone select element, but not as part of SPCascadeDropdowns, but something along this line 'should' help you, obviously substituting "mylist" for your select element's id value. Obviously this could be "smartened"
up a bit to use the displayname of the field as opposed to the ugly list ID string, but I didn't take it that far.

Thank you for the help. But I am really lost on this. I have researched more on the web to try and understand what each line is doing. Below is the first script that I have that is functioning to achieve the dropdowns.

You're part way there. The removeDuplicates function should be be before the </script> tag, so you've got that right. There is two things you've missed:

First, you need to add completefunc in the SPCascadeDropdowns call that will initiate the filter to remove the duplicates. This way, every time the city field is rebuilt by SPCascadeDropdowns the removeDuplicates function will fire to remove the duplicates.
Do this by adding the following above the debug: true line of the first SPCascadeDropdowns call:

completefunc: removeDuplicates,

Next, we need to update the removeDuplicates function a tad. The function I gave you won't just look for the City field, you'd have to get the field ID for the field from the form itself (I didn't go the whole way for you). Replace the $("City")
part of the third line of my function with the following:

I am still not getting anywhere with this. Of course there is no one in my Dev Group that has any clue what I am doing to help. So if you still have time to hold my hand through this I would appreciate it.

You've just got some issues with the way your functions are structured... You've got the removeDuplicates function inside the document.ready call... just have to close the document.ready call and close the removeDuplicates function. Try the version of your
code below:

I got an email from Marc about this also. He's away on vacation but he wanted me to point out that you're using an old alpha version of SPServices, which is really not advised in a production environment. You should grab the current version off the downloads
page.

Ok, I have updated all the software. Verified the names and the lists that I am using. I still cannot get the remove duplicate function to work. Do you know anywhere that I can look at that I might be able to troubleshoot this further. I hate to keep asking
for assistance on this since you probably get paid quite a bit for consulting work.

Replace the above removeDuplicates function with this. I've added an alert to it so we can see if it's getting called or not. See if you see the alert. If so, it's a problem within the removeDuplicates function, if not it's a problem within your SPServices
call...

Well now you should see a script error because you've got JavaScript that's just hanging out at the bottom. You need to remove the rest of the function too... the removeDuplicates function went all the way to the last }... should look like this:

Excellent, that's not an error, that's what we wanted to see. So your cascades work correctly and you see that prompt when you change the parent select box. That means that it is calling our removeDuplicates function, meaning that our error was somewhere
in that function that you removed as part of the last test. Let me look at that again...

The city field on the child site is called SiteCity, and it is a text field. On the parent site is called City and is a lookup column. I hope that is what you are asking. I am getting excited that you may have solved the great mystery here.

Alright, sorry for the holdup (had to run to a meeting), I think the holdup is in the selector for the city field (the field we're actually trying to remove the duplicates from.

I tested that removeDuplicates function and it worked, so the only variance is the actual name of the field. Can you confirm that "City" is the full displayName of the dropdown we're removing the duplicates from?

Here's a quick way to confirm it:

Right click on the page and view the page source.

Do a find on "City" and you should get to something that looks similar to the following:

I think that the issue with the duplicates is that you're trying to manage all of the relationships in the same list. If you look at the documentation page for
$().SPServices.SPCascadeDropdowns, you'll see that I recommend using one list to manage each relationship. This is good relational table design and will eliminate the duplicate issue altogether.

So, for what you are trying to accomplish, you'de have three lists: States, Cities, and Sites. States would just have the Title column which contains te names of the States. Cities would have the City names in the Title column, and a lookup column called
State which is a lookup to States:Title. Finally, Sites would have the Site names in the Title column and a lookup column called City which is a lookup to Cities:Title.

I gave in and went with seperate lists. I was trying to keep it as small as possible, but this works. I really appreciate your time and help on this, this will be a big hit with the business units I support.

On another subjuct, is there a way to update a comment box with a workflow or other means and not write over the previous comments? Kind of like the the versioning you get on a comment box but I would need to export all the data not just the last entry.

Not really, I have been struggling with this for a while. I love the way that SharePoint time stamps who and when a comment was made with versioning. The problem I have is due to Banking regulations I need to be able to export the entire history of the comments,
not just the last one.

One thought would be to capture the user comments on one column and then have a workflow append those comments with a timestamp to another column which is inaccessible on the forms, but visible in the views. If you have versioning on, that will of
course create a new version which may not be what you want.

You could also shove the whole document with it's history into the Records Center for storage ad infinitem.

Again, it all depends on what the actual record-keeping requirement is. I doubt that downloading to Excel covers the regulatory requirements.