We have had the same problem. Just copying the .ttf into the fonts directory is not enough. You also need to add some registry keys settings to get teh font to work correctly. Try copying in the font, use word etc to use it, which sometimes gets the font working initially. Then search the registry for the fonts filename, and hopefully that will return the reg keys you need to add, to get the font registering correctly when you first add the font. Roger Allen - Sonork 100.10016 Roger Wright: Remember to buckle up, please, and encourage your friends to do the same. It's not just about saving your life, but saving the quality of life for those you may leave behind...

Thanks, just what I was looking for.

You use include files to do this. So in your, lets say, default.asp page you will have that line of code where you want the contents of nav.asp to be inserted. You can then use it from multiple pages, one change to nav.asp will affect all the other pages. The include is inserted when the page is requested. regards, Paul Watson Bluegrass South Africa Marc Clifton wrote: "organically fed captivity free regurgitated bee nectar" (honey) on dieting. Crikey! ain't life grand?

NetUserAdd worked for me. "It was when I found out I could make mistakes that I knew I was on to something." -Ornette Coleman

Can you provide a few screen shots that exhibit the problem? I've never heard of such a thing.

Thank for the help. I had a problem in my code: MSDN Library: PRB: Modal Dialog Box Prevents Calls to PreTranslateMessage ID: Q126874

They leak every where, but WinNT/Win2000,WinXP system are use 32bit vales for addressing up to 2^32 GDI objects while 9x system uses just 16bit values, thus can hold only 2^16, which is much fewer. However that does not mean you can use the whole 4 billion GDI objects in WinNT systems, still the system put an upper limit but I do not know it exaclty, but I did encounter resource leak in WinXP before. check this MSDN article http://msdn.microsoft.com/msdnmag/issues/01/03/leaks/default.aspx Anyway, to detect resource leaks in Win2000/WinXP just open the task manger and go to the processes tab, then from from the "View" menu choose "Select Columns..." the check "GDI Objects". After that look up your process from the system processes and monitor its GDI Object, if they constantly increase then you have a leak, if it increase then stop increasing then it could just be initial allocations.

the first thing you need to do is to check for leaked GDI objects. -c When history comes, it always takes you by surprise. Bobber!