C / C++ / MFC

3-Nov-08 23:34

Hi,

I have created a User Interface which has a Help Menu in that i have USER Manual as submenu, when i click on User Manual sub menu it has to open an existing word document which contains details of how to use the User Interface. UI has been developed using MS VC++ .Please help me out.

Thanks in advance

enhzflep4-Nov-08 0:01

4-Nov-08 0:01

ShellExecute(NULL, "open", "pathToYourDocFile", NULL, NULL, SW_SHOWNORMAL);

See info on parameters here: MSDN: ShellExecute[^]

shir_k4-Nov-08 0:17

Re: Open word document on clicking menu [modified]

4-Nov-08 0:17

Thanks
I used the code sent by you but it not opening the document. Below is the code
void CNUITApp::OnHelpUsermanual()
{

ShellExecute(NULL, "open", "C:\\Doc1", NULL, NULL, SW_SHOWNORMAL);
// TODO: Add your command handler code here
AfxMessageBox(_T("Feature not available gg"),MB_OK|MB_ICONINFORMATION);
}

enhzflep4-Nov-08 0:23

4-Nov-08 0:23

Is your file really called "Doc1" ?

I suggest you use the following line:

Pre Office 2007

ShellExecute(NULL, "open", "C:\\Doc1.doc", NULL, NULL, SW_SHOWNORMAL);

or
Office 2007

ShellExecute(NULL, "open", "C:\\Doc1.docx", NULL, NULL, SW_SHOWNORMAL);

shir_k4-Nov-08 0:31

4-Nov-08 0:31

office 2003 is loaded in the system.
I will be giving only the exe to the customer, so we specify the path like this then we need to keep on changing the path where ever the document is copied. How to ovecome with this issue?

enhzflep4-Nov-08 0:57

4-Nov-08 0:57

Just use a relative path.

E.g

AppFolder
|
|--FolderA
|--FolderB
\--Help

if exe is located in AppFolder, and .DOC file is in Help folder:

ShellExecute(NULL, "open", "Help\\YourFile.doc", NULL, NULL, SW_SHOWNORMAL);

if exe is located in FolderA, and .DOC file is in AppFolder:

ShellExecute(NULL, "open", "..\\YourFile.doc", NULL, NULL, SW_SHOWNORMAL);

shir_k4-Nov-08 2:09

4-Nov-08 2:09

Thanks u vey much
Its working
The problem was path of the file
Thanks once again

enhzflep4-Nov-08 2:13

Memory Exception occur in case of Browse for Folder.

4-Nov-08 2:13

Pleasure.

Le@rner3-Nov-08 23:34

Le@rner

3-Nov-08 23:34

Hi all,

LPMALLOC pMalloc = NULL;
LPITEMIDLIST pidl = NULL;
BROWSEINFO bi;
ZeroMemory(&bi, sizeof(BROWSEINFO));

// set the bi's default values
bi.hwndOwner = m_hWnd;
bi.lpszTitle = _T("Current folder is:");
bi.ulFlags = BIF_RETURNONLYFSDIRS | BIF_STATUSTEXT;
bi.lpfn = BrowseCallbackProc;
pidl = SHBrowseForFolder(&bi);
if(pidl != NULL)
{
    SHGetPathFromIDList(pidl, m_strFolderPath.GetBuffer(m_strFolderPath.GetLength()));
    UpdateData(FALSE);
    // free memory
    if(SUCCEEDED(SHGetMalloc(&pMalloc)) && pMalloc);
    pMalloc->Free(pidl);
    pMalloc->Release();
}

i m using this for browse for folder,the out of memory exexption occur when select any folder.

please help me for this.

thanks in advance.

IN A DAY, WHEN YOU DON'T COME ACROSS ANY PROBLEMS - YOU CAN BE SURE THAT YOU ARE TRAVELLING IN A WRONG PATH

Re: Memory Exception occur in case of Browse for Folder.

CPallini3-Nov-08 23:57

CPallini

3-Nov-08 23:57

Why don't you release the CString buffer?
Smile | :)

If the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler.
-- Alfonso the Wise, 13th Century King of Castile.

This is going on my arrogant assumptions. You may have a superb reason why I'm completely wrong.
-- Iain Clarke

[My articles]

Re: Memory Exception occur in case of Browse for Folder.

Le@rner4-Nov-08 0:21

Le@rner

4-Nov-08 0:21

ok , now i am using

m_strFolderPath.ReleaseBuffer();

but problem remains same.

please help me for this.

IN A DAY, WHEN YOU DON'T COME ACROSS ANY PROBLEMS - YOU CAN BE SURE THAT YOU ARE TRAVELLING IN A WRONG PATH

Re: Memory Exception occur in case of Browse for Folder.

Rajesh R Subramanian4-Nov-08 0:40

Rajesh R Subramanian

4-Nov-08 0:40

Check this: How is SHBrowseForFolder() used?[^]

It is a crappy thing, but it's life -^ Carlo Pallini

Re: Memory Exception occur in case of Browse for Folder.

Le@rner4-Nov-08 0:59

Le@rner

4-Nov-08 0:59

thanks

IN A DAY, WHEN YOU DON'T COME ACROSS ANY PROBLEMS - YOU CAN BE SURE THAT YOU ARE TRAVELLING IN A WRONG PATH

Error while compiling code

izyani3-Nov-08 22:14

izyani

3-Nov-08 22:14

Hi,

I'm currently using Visual Studio 2005 to build my project.

The previous code that i have was written in Visual C++ 6.0. With the current development and tools, I already convert to project by using the Visual Studio 2005.

When i compiled my code, I got this error.

openssl.lib(v3_conf.obj) : error LNK2019: unresolved external symbol __pctype referenced in function _v3_generic_extension
openssl.lib(b_print.obj) : error LNK2001: unresolved external symbol __pctype
openssl.lib(obj_dat.obj) : error LNK2001: unresolved external symbol __pctype
openssl.lib(v3_utl.obj) : error LNK2001: unresolved external symbol __pctype
openssl.lib(bn_print.obj) : error LNK2001: unresolved external symbol __pctype
openssl.lib(v3_conf.obj) : error LNK2001: unresolved external symbol ___mb_cur_max
openssl.lib(b_print.obj) : error LNK2019: unresolved external symbol ___mb_cur_max referenced in function __dopr
openssl.lib(obj_dat.obj) : error LNK2001: unresolved external symbol ___mb_cur_max
openssl.lib(v3_utl.obj) : error LNK2001: unresolved external symbol ___mb_cur_max
openssl.lib(bn_print.obj) : error LNK2001: unresolved external symbol ___mb_cur_max
openssl.lib(rsa_sign.obj) : error LNK2019: unresolved external symbol __iob referenced in function _RSA_verify

I already check from the net. And I already ignore the lib : libcmt

Is there any thing that i can do to make it compile and works?

Thanks.

CPallini3-Nov-08 22:45

CPallini

3-Nov-08 22:45

izyani wrote:
Is there any thing that i can do to make it compile and works?

You should make it link, it already compiles.
You've to add the library wherein __pctype is defined in the Additional Dependencies line of the Linker's Input options.
Smile | :)

izyani4-Nov-08 14:47

izyani

4-Nov-08 14:47

Hi Pallini,
I already put the _pctype defined in the Additional Dependencies line of the Linker Input Option.

All error gone. But it create another error.

LINK : fatal error LNK1181: cannot open input file '_pctype.obj'

Do you have any idea?

Thanks

CPallini4-Nov-08 21:30

CPallini

4-Nov-08 21:30

You shouldn't do that, you should add the library containing _pctype definition.
You cannot add a type as input file for the linker!
Hint for the library name: usually it has the same name the include file has (for instance, if you include, say mylibrary.h, then there are odds the library file name is mylibrary.lib).
Smile | :)