C / C++ / MFC

Re: put_Collect & get_Colect ???

4-Jul-03 4:29

Most of the documentation you will find on ADO is in Visual Basic. When I learned I had to learn how to translate Visual Basic examples to visual c++. There is a class library on this site that uses ADO:

http://www.codeproject.com/database/caaadoclass1.asp[^]

John

Michael P Butler4-Jul-03 4:31

Michael P Butler

4-Jul-03 4:31

The names suggest that they are wrapper for the Collection property.

inline _variant_t Recordset15::GetCollect ( const _variant_t & Index ) {
    VARIANT _result;
    VariantInit(&_result);
    HRESULT _hr = get_Collect(Index, &_result);
    if (FAILED(_hr)) _com_issue_errorex(_hr, this, __uuidof(this));
    return _variant_t(_result, false);
}

inline void Recordset15::PutCollect ( const _variant_t & Index, const _variant_t & pvar ) {
    HRESULT _hr = put_Collect(Index, pvar);
    if (FAILED(_hr)) _com_issue_errorex(_hr, this, __uuidof(this));
}

I suppose the valuje of Index depends on the context of the Collection

Michael

'War is at best barbarism...Its glory is all moonshine. It is only those who have neither fired a shot nor heard the shrieks and groans of the wounded who cry aloud for blood, more vengeance, more desolation. War is hell.' - General William Sherman, 1879

Problem including commctrl.h.

blackmesa4-Jul-03 4:19

4-Jul-03 4:19

I always get these two errors when trying to include commctrl.h in my application.

c:\program files\microsoft visual studio\vc98\include\commctrl.h(26) : error C2146: syntax error : missing ';' before identifier 'HRESULT'
c:\program files\microsoft visual studio\vc98\include\commctrl.h(26) : fatal error C1004: unexpected end of file found
Error executing cl.exe.

I've added comctl32.lib to the list of library modules in my project settings, but it wouldn't resolve the problem. I use MS Visual C++ 6.0.

Any ideas?

Cheers, Blackmesa.

John M. Drescher4-Jul-03 4:32

4-Jul-03 4:32

Blackmesa wrote:
I've added comctl32.lib to the list of library modules in my project settings, but it wouldn't resolve the problem. I use MS Visual C++ 6.0.

Any ideas?

Your problem has nothing to do with linker settings. The problem is that you need some header included before commctrl.h. What type of project is this MFC, ATL, Win32 API... ?

John

blackmesa4-Jul-03 4:34

4-Jul-03 4:34

It's a WIN32 API project.

Cheers, Blackmesa.

John M. Drescher4-Jul-03 4:40

4-Jul-03 4:40

Do you have #include <windows.h> before #include <commctrl.h> ?

John

blackmesa4-Jul-03 4:42

4-Jul-03 4:42

The first #include in the incriminated file concerns commctrl.h, as you can see below.

/**
* input.cpp
*
* Input module.
**/

#include <commctrl.h>

#include "input.h"
#include "inputvars.h"
#include "gamevars.h"
#include "layout.h"
#include "resource.h"

//.... rest of file

Cheers, nickelplate.

Ryan Binns4-Jul-03 4:41

Ryan Binns

4-Jul-03 4:41

make sure you have included "winnt.h" or "wtypes.h" first. Does this help?

Ryan

Being little and getting pushed around by big guys all my life I guess I compensate by pushing electrons and holes around. What a bully I am, but I do enjoy making subatomic particles hop at my bidding - Roger Wright (2^nd April 2003, The Lounge)

Punctuality is only a virtue for those who aren't smart enough to think of good excuses for being late - John Nichol "Point Of Impact"

blackmesa4-Jul-03 4:45

4-Jul-03 4:45

After including wtypes.h, I have no more errors. Thanks a lot guys.

Cheers, nickelplate.

Ryan Binns4-Jul-03 4:55

Ryan Binns

4-Jul-03 4:55

You're welcome Smile | :)

Ryan

Being little and getting pushed around by big guys all my life I guess I compensate by pushing electrons and holes around. What a bully I am, but I do enjoy making subatomic particles hop at my bidding - Roger Wright (2^nd April 2003, The Lounge)

Punctuality is only a virtue for those who aren't smart enough to think of good excuses for being late - John Nichol "Point Of Impact"

Wide iostreams

Taka Muraoka4-Jul-03 4:06

4-Jul-03 4:06

You would think that the following bit of code would produce a 6-byte file:

wofstream f( "test.txt" ) ;
f << wstring( L"123" ) ;

But it doesn't. It produces a 3-byte file. A bit of experimentation indicates that the stream seems to be converting the wide characters to single-byte before writing it to the file. This also happens using Stlport (with their iostream library).

This seems just plain wrong. Anyone care to explain why it's like this?

Always code as if the person who ends up maintaining your code will be a violent psychopath who knows where you live.

Awasu 1.1[^]: A free RSS reader with support for Code Project.

Michael Dunn4-Jul-03 5:17

Michael Dunn

4-Jul-03 5:17

Curse you for making me look at the VC 6 STL code this early in the morning. Wink | ;)

The fstream inserter eventually calls basic_filebuf::overflow(), which has this line:

fwrite(_Str->begin(), 1, _N, _File)

The problem is that it writes 1 byte, when it should write sizeof(_E) [where _E is the template character type, wchar_t in this case].

--Mike--
"So where does that leave us? Well, it leaves us right back where we started, only more confused than before." -- Matt Gullett
Ericahist | Homepage | RightClick-Encrypt | 1ClickPicGrabber

Ryan Binns4-Jul-03 5:21

Ryan Binns

4-Jul-03 5:21

Michael Dunn wrote:
Curse you for making me look at the VC 6 STL code this early in the morning.

Laugh | :laugh:

Taka sent that message after midnight on a Friday night, so I don't want to know what he was thinking Wink | ;)

Taka Muraoka4-Jul-03 12:41

4-Jul-03 12:41

Ryan Binns wrote:
Taka sent that message after midnight on a Friday night, so I don't want to know what he was thinking

I'm converting Awasu to Unicode. My life is over until further notice Cry | :((

Actually, it's not quite that bad. Most of it is ready for Unicode but there are some core modules that I wrote years ago that need to be converted. Of course, *everything* uses them...

Always code as if the person who ends up maintaining your code will be a violent psychopath who knows where you live.

Awasu 1.1[^]: A free RSS reader with support for Code Project.

Taka Muraoka4-Jul-03 13:00

4-Jul-03 13:00

Michael Dunn wrote:
Curse you for making me look at the VC 6 STL code this early in the morning.

He he Smile | :)

Michael Dunn wrote:
fwrite(_Str->begin(), 1, _N, _File)

Yep. The odd thing is, Stlport does the same thing i.e. even when I use their iostreams instead of Microsoft's. They correctly process each character as 16-bit but then explicitly call codecvt to convert it 8-bit!

Which makes me wonder if this is what is supposed to happen. If this is a bug, it's a pretty obvious one and someone would've picked it up. Seems definitely wrong to me... Frown | :-(

Always code as if the person who ends up maintaining your code will be a violent psychopath who knows where you live.

Awasu 1.1[^]: A free RSS reader with support for Code Project.

Taka Muraoka4-Jul-03 15:08

4-Jul-03 15:08

This is just fscked!!!

According to this guy[^]:

The standard *does not* provide a way to output (i.e.: to write on a disk file) a stream of wide characters. You can put wide characters into a wide stream but you will always obtain a file of "narrow" characters, obtained through a "degenerate conversion" as explictly specified in the standard.

Also here[^]:

On Win32, VC++ 6sp5, STLport the following test program produces the output 52 (0x34) instead of 4660 (0x1234). According to the standard, this behaviour is perfectly conformant.

int main() { wchar_t a = L'\x1234'; std::wofstream out("test.txt", std::ios::binary); out << a; out.close(); std::wifstream in("test.txt", std::ios::binary); in >> a; in.close(); std::cout << unsigned(a) << std::endl; return 0; }

(The second poster also makes the interesting point:
the ios::binary is required, because the I/O library could apply CRLF translation to a part of a two-byte character.
)

This makes no sense. What possible justification could there be to have wide streams output narrow?! The only thing I can think of is possible problems with sending wide data to the console, for example, but surely it would be preferable to hack wcout et.al. rather than crippling wide streams! WTF | :WTF:

Always code as if the person who ends up maintaining your code will be a violent psychopath who knows where you live.

Awasu 1.1[^]: A free RSS reader with support for Code Project.

memory leak

pranavamhari4-Jul-03 3:31

pranavamhari

4-Jul-03 3:31

hi,

i need help from you guys again.

My program uses classes like CButtonST, AnyFormDialog, etc.
I am not blaming these classes, but i think my program is leaking memory. (found out using system monitor). when app closes, the memory is not released to the point where it was when launched.

now the question is how can i detect where in my application memory leaks? any free third party utilities ?

BTW, it leaks in ME, not in XP.

thanks for your reply.

Hari Krishnan

John M. Drescher4-Jul-03 3:53

4-Jul-03 3:53

Try http://www.softwareverify.com/download_eval.php[^]

You can get a free 30 eval which should be enough to solve your problem.

John

pranavamhari4-Jul-03 19:05

pranavamhari

4-Jul-03 19:05

thanks,

but as i said, it does'nt leak in XP. So i can't use this in my XP machine. It is leaking in ME only.

Also, i found out by trial and error that if i load the image from a file (~500KB) rather than a resource, it does'nt leak. Ofcourse i use DeleteObject() call at destruction when i load from resource.

regards

Hari Krishnan

John M. Drescher5-Jul-03 3:29

5-Jul-03 3:29

The thing I was going to tell you that is handled differently between windows NT ( NT 4, 2K, XP) and Win 9x is resources.

John

John

John M. Drescher5-Jul-03 3:30