C / C++ / MFC

Re: Filling out other application dialogs

23-Dec-02 11:37

You will to determine the window id of all the windows on the dialog you want to fill out and a handle to window you are filling out. Then simply use

::SetDlgItemText( hWnd, WindowId, "value" );

There was a password retival tool posted here, some of the code from it should help you to determine the window ids.

microcyb23-Dec-02 11:40

microcyb

23-Dec-02 11:40

Ahh I will continue to search, just had no clue what to search for.

would love to make it command lin based since it is to support at least 50 PC's.

Thanks for the direction!!!

PrintDlgEx, Visual C++ 6.0, and the Platform SDK

Jonathan Craig23-Dec-02 8:50

Jonathan Craig

23-Dec-02 8:50

I'm trying to use the PrintDlgEx method with Visual C++ 6.0. I have installed the Platform SDK (October 2002) and the include, lib, and exe directories for this are first in the directories option.

But I keep getting "error C2065: 'PRINTDLGEX' : undeclared identifier." It appears the complier is not look at the stuff in my "C:\Microsoft SDK" directories.

So what is required to get Visual C++ using the Platform SDK includes, libs, and exes?

Thanks for all input Wink | ;)

Jonathan Craig
www.mcw-tech.com

Re: PrintDlgEx, Visual C++ 6.0, and the Platform SDK

mwilliamson23-Dec-02 9:35

Re: PrintDlgEx, Visual C++ 6.0, and the Platform SDK

23-Dec-02 9:35

You must define _WIN_NT 0x500 in stdafx before you include the common dialog files. This means that your application will only run on windows 2000 / xp (which is when printdlgex as added).

Jonathan Craig23-Dec-02 10:15

Jonathan Craig

23-Dec-02 10:15

I don't see anywhere in the SDK include files a reference to _WIN_NT. I have added

#define _WIN32_WINNT 0x0500

and

#define WINVER 0x0500

to the stdafx.h file but I still get the same error.

Jonathan Craig
www.mcw-tech.com

Re: PrintDlgEx, Visual C++ 6.0, and the Platform SDK

mwilliamson23-Dec-02 11:13

Application Error only on some computers

23-Dec-02 11:13

Sorry, my mistake.

From CommDlg.h:

#if(WINVER >= 0x0500)
//
// PrintDlgEx structure.
//
typedef struct tagPDEXA {
DWORD lStructSize; // size of structure in bytes
HWND hwndOwner; // caller's window handle
HGLOBAL hDevMode; // handle to DevMode
HGLOBAL hDevNames; // handle to DevNames
HDC hDC; // printer DC/IC or NULL
DWORD Flags; // PD_ flags
DWORD Flags2; // reserved
DWORD ExclusionFlags; // items to exclude from driver pages
DWORD nPageRanges; // number of page ranges
DWORD nMaxPageRanges; // max number of page ranges
LPPRINTPAGERANGE lpPageRanges; // array of page ranges
DWORD nMinPage; // min page number
DWORD nMaxPage; // max page number
DWORD nCopies; // number of copies
HINSTANCE hInstance; // instance handle
LPCSTR lpPrintTemplateName; // template name for app specific area
LPUNKNOWN lpCallback; // app callback interface
DWORD nPropertyPages; // number of app property pages in lphPropertyPages
HPROPSHEETPAGE *lphPropertyPages; // array of app property page handles
DWORD nStartPage; // start page id
DWORD dwResultAction; // result action if S_OK is returned
} PRINTDLGEXA, *LPPRINTDLGEXA;
#endif

That means you need to define WINVER at 0x0500 before including Windows.h or CommDlg.h.

ElizabethC23-Dec-02 8:33

23-Dec-02 8:33

I have Dell with Windows 2000; the application is a MFC EXE developed using Visual C++ 6.0 enterprise.

After applying some modifications to the application, some of my client computers are receiving "Application Error" message. But this does not appeariing in the development computer.

The client computers and the developer computer have the same model and RAM size.

I am very frustrated. The "Application Error" is very difficult to trouble shoot.

Eilzabeth

Scott H. Settlemier23-Dec-02 8:39

Scott H. Settlemier

23-Dec-02 8:39

This sounds like a case for ....
CrashFinder[^]

Article here[^].

ElizabethC24-Dec-02 7:18

24-Dec-02 7:18

I downloaded and installed CrashFinder with the CLW file dated 5/6/2002. I received compilation errors:

Compiling...
CrashFinderDoc.cpp
C:\download\CrashFinder\CrashFinderDoc.cpp(1107) : error C2065: 'SymDia' : undeclared identifier
C:\download\CrashFinder\CrashFinderDoc.cpp(1107) : error C2051: case expression not constant
Error executing cl.exe.

Do I have the good version?

Eilzabeth

Scott H. Settlemier24-Dec-02 12:57

Scott H. Settlemier

24-Dec-02 12:57

That's a newer version. I think it must use an imagehelp.dll installed
with .Net or something. Try the older version available via the link in
the original article.

ElizabethC6-Jan-03 10:31

6-Jan-03 10:31

The problem is solved. The problem was in the Oracle ODBC driver. The client has an older version of the driver. After I upgraded the driver to version 9. The error went away. The problem was from one of the CLOB fields. I think some data is "bad" in that field because other CLOB fields do not cause problems. Thank you all very much for help.

-Elizabeth

Eilzabeth

mwilliamson23-Dec-02 9:39

23-Dec-02 9:39

Let drwatson write the log and then you can use it to find your problem. C:\Documents and Settings\All Users\Documents\DrWatson\drwtsn32.log. Goto the last crash, and it will tell you the call stack around the crash. You will see fault in the margin for the line on which it crashed. Hopefully you will have enough information to trace it back to a line in your source. If not, build your release with debug information. Then let it crash, you should now see what function caused the crash and in what windows function. You might want to do this off the bat because drwatson is usually hard to read.

ElizabethC24-Dec-02 7:26

24-Dec-02 7:26

I went to the folder and found drwtsn32.log. But it was created in 2001. Do I have to turn it on some how?

I also modified the project setting to include the debug information. Hope it will help when my client comes back from vacation.

Eilzabeth

ElizabethC6-Jan-03 10:35