solution 2: if you decide to use a windows program then you can get main like argv list by using the CommandLineToArgvW()[^] function. Note that this function has only widechar (utf16) version so you might have to convert the argv values to whatever encoding you use with the WideCharToMultiByte()[^] function before you call your console main().
This come because your code has error(s). This will go away when you fix the problem.
I don't know what this BEX is you speak of - you've not put it in context! It could be for BeX analyzer, it could be for BeX query designer, it could be for something to do with Excel. It could very well be for none of these! You already know, we can't possibly have any idea..
From the code snippet you (didn't) post, it's more difficult than impossible to tell. When you ask a specific question and provide sufficient background information, you'll (often) receive a specific answer.
As Peter said - you've been here nearly 5 years! Surely you can muster up the effort required to post a question that is able to be answered???
Why is common sense not common? Never argue with an idiot. They will drag you down to their level where they are an expert. Sometimes it takes a lot of work to be lazy Please stand in front of my pistol, smile and wait for the flash - JSOP 2012
I am trying to call the DisableProcessWindowsGhosting() method defined in user32.lib. But, it is giving linker error: [exec] dobjedit.obj : error LNK2001: unresolved external symbol __imp__DisableProcessWindowsGhosting@0. The library is included and linked in the project. Can anyone please suggest the solution.
I have a win32 application in that on EditMolecule Dialog there are three tab controls.First tab control opens atom dialog. On atom dialog, there is a custom combobox control, while user clicks on the dropdownlist of this control and waits for more than 5 seconds(in Windows7),the EditMolecule window becomes nonresponsive. The same application works well in windows xp. Can anyone please suggest the solution to this problem. Thanks in advance.
Your program has a platform specific bug somewhere and you have to debug it. The info you provided is far less than what needed to find the bug. This bug can be anywhere in your program maybe it isn't gui related at all.
we are not able to reproduce the issue using windebug. The debugger is not breaking. Could you please suggest what can be the possible reason, because after attaching the process to debugger the issue is not reproducible.
From the above it's impossible to guess, but you need to look at all the parameters being passed to the WinMain() function to see if they are valid. Given the frequency of this occurring in your programs you may like to check that you are not breaking the framework rules somewhere in your program setup.
One of these days I'm going to think of a really clever signature.