Userphobia ? ;P The tigress is here :-D

No wrrieos. Wre'e jsut tkinag the psis out of you :) Cheers, Tom Archer Inside C#, Extending MFC Applications with the .NET Framework It's better to listen to others than to speak, because I already know what I'm going to say anyway. - Jörgen Sigvardsson

Nope, I don't think so:(, but you could always buy a new one "If teenagers got no brains, what would I be than writing articles on C++? A genious??" :rolleyes: -DevHead "Humans often have an SBH relationship: Shag it, breakfast, had it." -DevHead "Mathemathics is incorrect: Take one male pair of brains, and one female pair of brains, add them and you'll have 0 pairs of brains." -DevHead

As others have pointed out, IMO it's a matter of liability. I find nothing wrong with the utility, per se, but you've posted it on the main page of your company's web site. If that doesn't have "endorsed" written all over it, I don't know what does. To anyone who knows nothing about "Psychosoft Pty. Ltd.", this is what they produce and market. Well, obviously, even for those who know nothing about the company, there's gotta be more to it than this one small utility, but the impression it makes is that the utility is part of it. I've learned a long time ago to distance myself, as a developer, from the company I work for--I don't represent them and they shouldn't be held liable for any of the little utilities I write in my spare time. I've written plenty of quick-and-dirty utilities (none with a "proper" setup program or even a readme), but I went out of my way to ensure than none of them would ever be associated with the company I work for, past, present or future. At a minimum, if you want to put your utility "out there", and insist on using your company's web site as a host, then the minimum you should do is not to post a link to it. If you want to share it with your friends, provide them with a direct link in an email or such--but don't post a URL to the main page of your company's site. If, on the other hand, you *want* as many people as possible to try out your utility, then make the disclaimers obvious. And as a golden rule, don't use your company's name in your own personal projects. Ever.

As you have correctly pointed out. SQL Server 2000 doesn't allow table variables as input parameters in stored procedures. What you could use instead is the "politically correct" xml document. Pass an xml document (array... ) to the SQL Server, and use the OPENXML statement to process it. :) Morty

Thank you, thank you, thank you! :-D

Roger Wright wrote: Nah, he wrote those right off the top of his head. John's a very talented guy And he practices each and every phrase! :laugh: :omg: Eddie Velasquez: A Squeezed Devil Checkout General Guidelines for C# Class Implementation

Would this not just retrieve the Date for when each defect was last issued? What I require is a list of defects for which the last action was to issue them, and i require the Date at which this took place. I imagine this is hard to understand without a more verbose description of the problem. Perhaps explaining an analogous situation could help: A table of employee details as follows: DepartmentCode Name Salary 1 Alex 40000 1 Kevin 30000 1 Mark 20000 2 Bruce 50000 2 John 60000 3 Michael 70000 Say I want to find the employees in each Department with the highest salary. I could do: SELECT DepartmentCode, MAX(Salary) FROM employees GROUP BY DepartmentCode to get a table with DepartmentCode and Salary, but how can i also get the Name of the highest paid person? The Name is analogous to my StatusCode, if i can get the StatusCode in the results i can use perhaps a HAVING clause to eliminate the ones that are not "ISS". I hope this makes things clearer Thanks for your help :) ~Alex

Have you merged the .PBO file yet? Perhaps doing a 'prep /M filename' will fix it. Otherwise I don't know... /moliate

Use WaitForInputIdle. Tomasz Sowinski -- http://www.shooltz.com

Check out WM_PRINT - it renders a window into a DC that you supply. --Mike-- http://home.inreach.com/mdunn/ This must be Thursday. I never could get the hang of Thursdays...