Perhaps something like this will work for you. Sub CopyDoc() ' save a reference to the source document Dim sourcedoc As Document Set sourcedoc = Application.ActiveDocument ' create a new document with the same template as the source document Dim newdoc As Document Set newdoc = Application.Documents.Add(Template:=sourcedoc.AttachedTemplate.FullName, Visible:=True) ' copy sourcedoc and paste in newdoc sourcedoc.Range.Copy newdoc.Range.Paste sourcedoc.Activate Set sourcedoc = Nothing Set newdoc = Nothing End Sub

rbid wrote: Question: Can we use this #pragma comment(ignore 4089) for the warning related to "OLEAUT32.dll" only? no. rbid wrote: or what I understand, the use of the #pragma is the same as hiding the warning via /IGNORE:4089 in the project settings exactly. rbid wrote: Does anybody has another suggestion? there's no other way. either you hide every 4089 warnings, or you show them all. but hey, it's only a warning, why do you bother that much ? [VisualCalc][Binary Guide][CommDialogs] | [Forums Guidelines]

Well I didn't know there was a control beneath where you need to click :) In that case you'd need to catch it at the control since that's where the click message goes. So I guess in that case, maybe an owner-drawn control that draws nothing is a worthwile solution. Mark "Posting a VB.NET question in the C++ forum will end in tears." Chris Maunder

Hello to all, First of all, thanks for your help in trying to solve this problem. The problem is solved, and was caused by variable aliasing that confused the compiler optimizations. The code that caused the problem has been re-designed and fixed. (I found also other spaguetti programming problems there). How was this problem isolated First I added to the beginning and end of all source files (not header files) the following line: // Add at the beggining of the file: #pragma optimize( "", off ) ... // Add at the end of the file: #pragma optimize ("", on ) Then file by file, once a time I removed the pragma to see if the problem appears, if yes, mark the file as problematic and continue to the next file.(restoring the #pragma to the beggining of it) Once I finished with all files, and ending with a pair of problematic files, I started to do the same for isolating the "functions" that caused the problem. // Add before the function body: #pragma optimize( "", off ) ... // Add after the function closinc brace: #pragma optimize ("", on ) At the end, I found that only a small number of functions were the ones that caused the problem, and the reason was variable aliasing. The code was belonging to a novice developer, that with my help he has re-designed his code and now we all are happy :) Note: Variable aliasing is described in the VC documentation, look under Compiler Optimizations, specially for the flags /Ow or /Oa. Thanks to all who helped me to identify the problem. -- **Ricky Marek** (_AKA: rbid_) -- "Things are only impossible until they are not" --- Jean-Luc Picard My articles

It is so simple when you know it :) -- **Ricky Marek** (_AKA: rbid_) -- "Things are only impossible until they are not" --- Jean-Luc Picard My articles

Ah. Sorry, I was hasty in replying! :-O /ravi My new year's resolution: 2048 x 1536 Home | Articles | Freeware | Music ravib@ravib.com

I'm not sure about VC 7.1 but with VS6, I have a class with two methods, each overloaded several dozens of times. Twelve seems awfully skimpy. "Opinions are neither right nor wrong. I cannot change your opinion. I can, however, change what influences your opinion." - David Crow

Be aware that if you define your own overloaded operators &&, || etc. that they will NOT short-circuit! Cheers Steen. "To claim that computer games influence children is ridiculous. If Pacman had influenced children born in the 80'ies we would see a lot of youngsters running around in dark rooms eating pills while listening to monotonous music"

I have played around a bit with inverting frame-grabbed images, and I found that the XOR technique usually works nicely. Where it will not work well is with grey-scales which are close to mid-range, for example, if you have RGB-15 (5-bits of each colour, high order bit unused), where the R, G, and B values are all half-range = 15 decimal, i.e. the pixel is 0011 1101 1110 1111, XORing will give 1100 0010 0001 0000, i.e R, G, and B are all 10000 binary = 16 decimal. For cases like this, the XORed text will be very difficult to make out. To get around this, you could saturate (force to maximum or minimum) each colour component, then XOR / invert the result. For my example, the 15 decimal component values are forced to 0, then inverted to give 11111 binary, which should be visible.

rbid wrote: Is it possible to delete a pair without renaming the following keys? I just tried, and the result is that VC will truncate the list at the first empty place, that is, if you delete item3, (File3 key), the start page will only show the first two items.:( -- **Ricky Marek** (_AKA: rbid_) -- "Things are only impossible until they are not" --- Jean-Luc Picard My articles

rbid wrote: don't need to be 'on-line' all the time, or even every day for catching the notifications. If you don't need to be notified immediately, why don't you subscribe to the weekly CP newsletter? Here's a trick for "the real programmer": Write the titles of all interesting articles in to text file. When your mail client has downloaded a CP newsletter, run a script that finds the newsletter in the inbox, searches for the titles from the text file, and deletes the newsletter if none of the titles is found. For Thunderbird: The mails are in a plain text file called "Inbox" in your profile directory. For Outlook: Try a VBA script. :cool: :-D _________________________________ Vote '1' if you're too lazy for a discussion

That's useful to know. :cool: I'm not surprised they've found bugs using it - the alternative approach (Lint) in its raw form is not easy to set up, and on a large codebase it can be very hard to use it effectively without a concerted effort. That's something we're specifically trying to address, but of course we'll certainly look at other approaches to see what they offer! Anna :rose: Riverblade Ltd - Software Consultancy Services Anna's Place | Tears and Laughter "Be yourself - not what others think you should be" - Marcia Graesch "Anna's just a sexy-looking lesbian tart" - A friend, trying to wind me up. It didn't work.

Create your own button class CMyButton, which subclasses the existing CButton. Add a handler for the WM_LBUTTONDOWN message to CMyButton. In the handler, post a notification to the parent dialog like this: WPARAM wParam = MAKEWPARAM(GetDlgCtrlID(),BN\_PRESSED); LPARAM lParam = (LPARAM)m\_hWnd; GetParent()->PostMessage(WM\_COMMAND,wParam,lParam); where BN_PRESSED is a notification code you've defined. In your dialog, add a handler for the BN_PRESSED notification. In the handler, start a timer (try using QueryPerformanceCounter). In your BN_CLICKED handler, get the value of the timer and compare the difference. Software Zen: delete this;

have you tried calling UpdateWindow()? My articles www.stillwaterexpress.com BlackDice