Like a virus or tracker. Can I have the link please!!

ok, sir. I was rush, but the good point is that i asked you before posting an answer. i wish that Manfred didn't see it (i'll kill you if you told him) ;) Help people,so poeple can help you.

pstsp911 wrote: Is it possible to access local machine form webpage without IE/ActiveX? If it were, lots of harddisks would have been formatted from there. I are Troll :suss:

It's easy with the right approach: Position the leaves first. If each leaf has its own space in the Y dimension (i.e. no other nodes under it), you can easily assign Y coordinates for all the leaves. Just go through them from left to right, incrementing the Y coordinate according to each leaf's width and the gap between adjacent leaves. The X coordinates come from the leaves' depths. The next step is to assign coordinates to the interior nodes. One approach is to position each interior node in the middle above its leaves. Finally go through all the nodes, drawing them at their assigned coordinates, and drawing links from each interior node to its children.

How's about this? SELECT ID=MAX(Agent.ID) ,FirstName=MAX(Agent.FirstName) ,LastName=MAX(Agent.SecondName) ,Sold=SUM(CASE Seller WHEN Agent.ID THEN 1 ELSE 0 END) ,Bought=SUM(CASE Buyer WHEN Agent.ID THEN 1 ELSE 0 END) FROM Agent LEFT OUTER JOIN [Order] ON Agent.ID=[Order].Seller OR Agent.ID=[Order].Buyer GROUP BY Agent.ID :-D (And, yeah, be sure to index Buyer and Seller)

I think your data design may be flawed (I don't know your business so I cannot be more definite), the ShipID on your customer table makes me suspicious that you are creating a new customer per order. You should have at least 3 tables to support an order processing system. Customer, Order and OrderLines. 100k customers per month also makes me suspicious of your structure. 100k records per month is not a large volume (for SQL Server, I don't use express) and I would look to archiving annually rather than monthly. Then I'd use an OLAP cube to retain reporting infrastructure. Promoted is a flag/attribute of the Customer table, not a separate table. Remember every field does not need to be filled in the table. I would make the promoted field a date field giving you the option of making time based queries. Never underestimate the power of human stupidity RAH

For an internal app, I generally just connect to the database from the client.