In that case, you're on your own. You'll have to consult with the docs on the API to find out if the datetime your getting is in any specifal format, not culture specific, or it it'll give you the culture info. I'm doubting it though. Dave Kreskowiak Microsoft MVP - Visual Basic

I use COM inside .NET because I am just testing ADO with dBase IV files. This sample code is just a test application. The main application where the performance of ADO is critical is written in VBA, so I have to use standard COM objects. During my tests, I have discovered an abnormal behaviour of my test application: I have several standard machines (WinXP SP2, MDAC 2.8, etc...) and in one of them it works properly. It's quite strange because in that one, the driver doesn't accept file names longer than 8 chars (defined as DOS 8.3 standard names). I've checked all drivers version and it seems they are the same in every machine. Does anyone know which package (or settings) could make this possible?

Hi there, You might consider using the dcomcnfg.exe tool (or go to Control Panel/Administrative Tools/Component Services) to grant the ASP.NET process identity the permission to launch and activate that COM object.

Code is manuf[i] = strdup("Hello"); the function provides to create a location of memory where it copies the string and writes the address of that location on the pointer manuf[i]

hmmmmmm your code works on my machine. i feel that there is something wrong, but i cant figure it out. but here is a suggestion: are u sure that scanf places a null-terminating character at the end of the buffer? if it does not, initialize the buffer to zeros. Thats all i have my apologises, Mohammad

Use ShellExecute() or ShellExecuteEx(). "You're obviously a superstar." - Christian Graus about me - 12 Feb '03 "Obviously ???  You're definitely a superstar!!!" mYkel - 21 Jun '04 Within you lies the power for good - Use it!

I've not tried this exact thing, but have done something similar. Derive a class from CFileDialog. At the end of the OnInitDialog() method, post a message. In the handler for that message, call ShowWindow(..., SW_HIDE) on the control you want to hide. If you are not using MFC, you can do the same thing using GetOpenFileName(). Just specify a hook procedure in the lpfnHook member variable. In the hook procedure, handle the WM_INITDIALOG by posting the same message as mentioned before. Hopefully this will solve your problem, or at least point you down the right path. "Opinions are neither right nor wrong. I cannot change your opinion. I can, however, change what influences your opinion." - David Crow

One solution is to declare the global variable in stdafx.h. Kuphryn

I was thinking more along the lines of this:void CMyClass::OnButtonStart() { AfxBeginThread(FillListView,this); } UINT ListView(* pClass) **//forgot how the function declaration has to be**:zzz: { CMyClass* pMyClass = (CMyClass*)pClass; pClass->Num = 0; char* ptrItem; while (pClass->Num < 100) { itoa(pClass->Num,ptrItem,10); pClass->myLC.InsertItem(Num,ptrItem); pClass->Num++; } return 0; } the syntax may be a little off since I'm doing it out of my head, but I think you should be able to follow what I'm saying. I hope this helps in any way. If I write code in my sleep, does that make me brilliant, or just a lazy programmer? My articles www.stillwaterexpress.com BlackDice - the programmer formerly known as bdiamond

I've already tried this way, but the result was the same. I solved the problem in another way. Thanks to everyone

You are most likely writing past the end of an allocating heap block. You need to work through your code and try and track the cause down. There are various CRT Heap Debugging functions that will help with this. Google "crt debug heap" for help on this. Neville Franks, Author of ED for Windows www.getsoft.com and Surfulater www.surfulater.com "Save what you Surf"