The problem is that the toolbar is variable....the buttons that would appear in the toolbar, as well as their order, are variable. In addition, I already have several dozen ico files which would all have to be mushed together into one big bitmap.

Ok, me again. Worked out the following. You can install BOTH MSDN Oct and MSDN Jan 2k2 on the same machine - and they work with both VS .NET and VS 6. Yay! We're using a network install here so the total cost of having VS .NET plus two MSDN 'lite' installs is about 1 GIG. Works for me.. Timbo :omg: :rolleyes: :laugh: :rolleyes: :omg:

Hello Ron. I haven't had this particular problem lately and like you say I can't see it being a resource problem. But, I used to have trouble with an old Windows and to save me going in and out of Windows to run nmake, I split my make file. Then did an Nmake of mafefiles, sort of thing. To get yourself going I would do that very thing again. Though I am a touch worried that you say the problem seems to hinge arround one of three files. I would do a build of those you suspect and at least one before (thinking of the likely order of build) with full warnings switched on , I know you have to plough through junk too with this build, but as you do consider an old type problem, where you used to get a corrupt byte in the source file that confused the compilers. Even notepad is capable of this. Mike. Are you saying that MS have got their cl.exe running at kernal-0 level? I would find that difficult to believe, or maybe your saying that a call it happens to make hi-lights a kernal bug? We do it for the joy of seeing the users struggle.

The definition of the datatype has to be added to the interface and the pointer should be of that datatype. Then you can pass custom datatypes. In MSDN index, type in "struct", it will bring up one for IDL/MIDL. You should be able to take it up from there. - Thomas