C / C++ / MFC

1-Jun-05 10:03

I have come across a function that looks like a member function being called but there is no class being declared before it, just the two '::'. How does this work?

Thank-you

Roland Pibinger1-Jun-05 10:09

Roland Pibinger

1-Jun-05 10:09

It only means that myFunc isn't in a namespace ("no_namespace"::myFunc).

Nilesh K.1-Jun-05 17:47

Nilesh K.

1-Jun-05 17:47

It means that the function is part of global namespace.

<bold>- Nilesh
<italics>
"Reading made Don Quixote a gentleman. Believing what he read made him mad" -George Bernard Shaw

toxcct1-Jun-05 21:08

toxcct

1-Jun-05 21:08

i'd like to add a little precision... there are 2 scope operators

- the class scope (class::member)
- the global scope (::global_obj)

cheers,

TOXCCT >>> GEII power
[toxcct][VisualCalc]

Executing a program from within mine

trelliot3-Jun-05 20:45

trelliot

3-Jun-05 20:45

Wrong - there is only 1 scope operator, but there may be 0 or more namespaces or classes, so that without a modifier, the instance refers to the global namespace, i.e. all publically decared functions as might be declared within your own programme or any libraries linked to your programme.

Anonymous1-Jun-05 9:23

1-Jun-05 9:23

What's the command to start a program from within my program?

ddmcr1-Jun-05 9:35

ddmcr

1-Jun-05 9:35

use WinExec() function
ex :

WinExec("C:\\Path\\program.exe",0);<br />

"Go as far as you can see,and when you get there you’ll see further" - Unknown

Anonymous1-Jun-05 9:47

1-Jun-05 9:47

I guess that's what I was looking for, but it doesn't go all the way. For example, I'd like to be able to close my program and have the other one still running. (When attempting this, the window of the other program also didn't become visible.)

Wes Aday1-Jun-05 9:55

Wes Aday

1-Jun-05 9:55

Anonymous wrote:
but it doesn't go all the way

Have you tried ShellExecute?

Artificial intelligence is no match for natural
stupidity.

Never argue with an idiot. They will drag you down to their level where they are an expert.

ThatsAlok1-Jun-05 18:31

ThatsAlok

1-Jun-05 18:31

Anonymous wrote:
I'd like to be able to close my program and have the other one still running

CreateProcess will Help in this case, When you use CreateProcess to Execute a Executable, one of it's parameter i.e. LPPROCESS_INFORMATION parameter return with PROCESSID.

Using that Parameter you can control that process i.e.
For terminating the Process :- [TerminateProcess()]

"Opinions are neither right nor wrong. I cannot change your opinion. I can, however, change what influences your opinion." - David Crow

cheers,
Alok Gupta

Miszou1-Jun-05 10:01

Miszou

1-Jun-05 10:01

From MSDN:
WinExec is provided only for compatibility with 16-bit Windows. Applications should use the CreateProcess function.

Or alternatively, use ShellExecute, which is a "simpler" function call than CreateProcess.

The StartPage Randomizer

racenjason1-Jun-05 11:47

racenjason

1-Jun-05 11:47

This code will open a program, open a url, open a file, really open anything that has an associated File Type in the registry and Windows knows what to do with it...and it doesn't matter whether you close your program or not. I only call it OpenURL because that is what I mostly use the function for

BOOL CGlobals::OpenURL(CString csURL)
{
SHELLEXECUTEINFO UrlInfo;
memset(&UrlInfo, 0, sizeof(SHELLEXECUTEINFO));

UrlInfo.cbSize = sizeof(SHELLEXECUTEINFO);
UrlInfo.lpFile = (LPCTSTR)csURL;

// TRUE = explorer/netscape window opened (doesn't check for url connection)
return ShellExecuteEx(&UrlInfo);
}

Enumerating ODBC drivers...

trelliot1-Jun-05 22:01

trelliot

1-Jun-05 22:01

// Here's a start:

// Run an external command, optionally waiting around
// for it to finish.
bool RunProgram(LPCTSTR progName, LPCTSTR args,
bool wait /*=false*/, int show /*=SW_SHOWNORMAL*/,
)
{
CString commandLine, userName;
PROCESS_INFORMATION procInfo;
STARTUPINFO startInfo;

memset(&startInfo, 0, sizeof(startInfo));
startInfo.cb = sizeof(startInfo);
startInfo.wShowWindow = (WORD)show;
startInfo.dwFlags = STARTF_USESHOWWINDOW | STARTF_FORCEONFEEDBACK;

try
{
// remove leading and trailing spaces
// Trim() is left as an excercise for the reader
commandLine = Trim(progName);
// If there's a space and no double quotes,
// surround the command with double quotes
if (commandLine.Find(' ') >= 0 && commandLine.Find('"') < 0)
commandLine = '"' + commandLine + '"';

commandLine += ' ';
commandLine += args;

LPTSTR lpCommandLine = commandLine.GetBuffer(CommandLine.GetLength() + 32);
if (!CreateProcess(NULL, lpCommandLine, NULL, NULL,
FALSE, 0, NULL, NULL, &startInfo, &procInfo))
return false;

if (wait)
WaitForSingleObject(procInfo.hProcess, INFINITE);

CloseHandle(procInfo.hThread);
CloseHandle(procInfo.hProcess);
}
catch(CMemoryException *)
{
return false;
}

return true;
}

dandy721-Jun-05 8:25

dandy72

1-Jun-05 8:25

Hi all,

I need to programmatically enumerate all ODBC drivers installed on a machine. I found some samples, and they work well enough, however I can't find an awful lot of "official" Microsoft documentation on the ODBC APIs themselves.

For example, one of the samples I found uses an API called SQLDrivers(). No problem, it's defined in the latest Platform SDK in sqlext.h. Looking this up in the January 2005 edition of the MSDN library, I'm brought to Servers and Enterprise Development|SQL Server|SQL Server 2000|SDK Documentation|Building SQL Server Applications|ODBC and SQL Server|SQL Server ODBC Driver Programmer's Reference|ODBC API Implementation Details|SQLDrivers, which simply states:

"The ODBC Driver Manager returns all ODBC 3.0-defined SQLDrivers attribute specification strings. For more information about attribute string and value definition, see the ODBC 3.0 documentation."

I'm looking for the actual MS documentation that goes over all the parameters, value returned, possible errors, etc. Where the hell is this??

Re: Enumerating ODBC drivers...

trelliot1-Jun-05 22:13

trelliot

1-Jun-05 22:13

I don't think I can help a lot, but maybe you should be looking at SQLBrowseConnect

Re: Enumerating ODBC drivers...

dandy722-Jun-05 3:18

dandy72

2-Jun-05 3:18

> I don't think I can help a lot, but maybe you should be looking at SQLBrowseConnect

I think you misunderstood my question...I don't have any problem enumerating ODBC drivers, per se, but rather I was trying to look for parameter/return value documentation for those SQL*() set of APIs. The section of the MSDN documentation I was looking at essentially describes what the functions do, but do not go into any amount of detail as to what the parameters are, the values returned, error conditions, etc.

For the record, I did find what I was looking for by doing an actual search D'Oh! | :doh:

It's all under (again, MSDN Library Jan 2005) Win32 and COM Development|Data Access and Storage|Microosft ODBC|Microsoft ODBC|ODBC Programmer's Reference|Part 4 - API Reference|ODBC API Reference.

The funny thing is that with the documentation tree structure opened on both locations, I can see all the same functions being listed twice. Why MS can't organize this better is beyond me...

Tooltip without hwnd?

Anonymous1-Jun-05 8:21