AFAIK, if you're using Microsoft IIS you can add php interpreter, and that way you can mix php, jscript and vbscript. With full access to functions/variables in either. (within the same ASP file) Access to functions located in other files can be achieved with *includes* directives, which load the external file into the current web server code. Q. Hey man! have you sorted out the finite soup machine? A. Why yes, it's celery or tomato.

hrishi321 wrote: I am looking for something efficient and easy to use. May be less code. Based on the following parameters, my suggestions would be: 1. Use a DataGrid and not a simple table to avoid extra code 2. Implement server side pagination such that each page is fetched on-demand 3. Use client side techniques to update the grid - jQuery AJAX, ASP.NET AJAX, Callback, WebMethods, etc. One mistake in your question: "Client-side pagination" => that means whole data in one go and on page change no data fetched from server. That would not be needed. Sandeep Mewara [My last tip/trick]: Server side Delimiters in ASP.NET[^]

Refer this simple example, showing the usage of gridview http://www.csharpaspnetarticles.com/2009/07/display-images-gridview-from-database.html[^]

Have you looked at this article[^]? CQ de W5ALT Walt Fair, Jr., P. E. Comport Computing Specializing in Technical Engineering Software

I think you need to bite the bullet and convert all your char variables and constants to TCHAR. If you do not, you will continue to have problems like this. If it were easy to solve the multi-byte to Unicode to multi-byte character conversion issues that solution would be part of the CString class. The changes you need to make are mechanical. You need to put _T() around all your string and character literals. You need to change all your char variables to TCHAR. I don't know how big your project is, or if you have access to all the source. I suspect you have spent more time trying to avoid the issue than a proper fix would require.

Why did you post that as a reply to me?

Your basic problem appears to be to understand how Header Files, cpp Files, the Compiler and the Linker work. First the Compiler. The Compiler builds an Object File. This is a Binary representation of a cpp File. It containd the CPP Code you wrote, converted to machine code as well as a whole raft of information needed later. The Compiler contains a thing, called a Pre-Processor. It prepares your CPP file before actual compilation. Conceptually it produces a New Source File. It copies your file Line by Line. but if it finds a statement like #include "MyBeautifulHdr.h", it does not copy the include statement, but, instead writes the entire contents of "MyBeautifulHdr.h" at the location of the '#include' statement. When it encounters a #define FOO 1 statement, it undertakes to replace henceforth every future occurrence of 'FOO' with 1. It goes on like that at infinitum, and the final file offered to the compiler has all '#includes, #defines, #if's etc resolved. At that stage the compiler does not know ( and does not care) from what file what item came from, (except for error reporting). It just builds the Object File, (if it Can) if it cannot, you get an error. Each of the Object Files generated roughly correspond to the code you wrote in a cpp file. An extern declaration is a promise to the compiler that somewhere in an other file or library, an item of that specification exists. The Linker tries to build an executable out of all those object files. In doing so, it may also include Object files written by others, e.g. those written by Microsoft, which came with your compiler package. To make that process more efficient, multiple obj files can be gathered together into a library (.lib) file If the linker cannot find a named item, or, finds more than one, the linker will fail building the executable. Getting a Full understanding of how your tools work will answer your queery. regards, :) Bram van Kampen

Why do you want to do that! Horses for Courses. Do you also want to migrate from Exel to Word? Regards, :) Bram van Kampen

Adobe Dreamweaver is a commercial product. There are demo versions you can download and use for a limited amount of time. So if you want to use it after the demo version expires, you will have to buy it.

yep.. got it from Rajeesh's post :thumbsup:

"use XYZ in a efficient way" :-O :-O :-O Press F1 for help or google it. Greetings from Germany

From experience I've settled on three classes: 1.CMessage: containing the description of an error, though a message doesn't have to describe just an error - "Application started" and "Application stopped", for example, can be included alongside "Widgit X fell over". Initially I used a .h file for this but migrated to using a .mc file as well, the .mc being compiled to produce a .rc resource file. 2.CEventLog: containing some means of logging a message. I started logging to a .txt file, moved to .html and now log to the Windows Event Log via the ReportEvent [^] function. 3.CExError which can be thrown and has a constructor which takes the error information and logs it. The most productive tactic by far I found was to ensure the file and line numbers where the error occurred were included in the message by using macros such as: #define AT __FILE__ ":" TOSTRING(__LINE__) Importantly I found this was a maintainable and expandable (relatively easy to add or edit messages) strategy which: 1. Didn't obscure the actual point of the code (too much) with line after line of error handling. 2. Completely hid away logging of errors in the CExError constructor, 3. Moved away (to the catch block) the point at which any code written to recover needed to go. So the actual code ended looking something like: ... void someclass::somefunction(...) { try { if(!AttemptSomething(param1, param2) { throw CExError(MESSAGE\_ID\_1, "Context info", AT); } if(!AttemptSomethingelse(param1, param2) { throw CExError(MESSAGE\_ID\_2, "Context info", AT); } } catch(CExError& err) { //Decide what to do about any error here, such as: if(MESSAGE\_ID\_2 == err.MessageID) { MessageBox(err.Message); } } return; } ...

hrishi321 wrote: wheneerv a message comes i want to put in a queue..and the reciever function returns the control...now i want to have a thread, which will keep looking onto the queue...if empty, do nothing....if not empty then process the message.... That's what the UI thread does (if you're using MFC). hrishi321 wrote: main reason to do this is...instead of having the while loop in the thread function, which will eat CPU cycle, i want some mechanism to do task only when needed)... WaitForSingleObject[^] could help you do this. A queued event thread is fairly easy to implement if you're not using MFC as well. All you need is a thread, a message queue and a couple of events that signals if there's more messages to be processed and if the thread should stop execution immediately (app shut down) and a WaitForSingleObject (or multiple objects, depending on how you do it) call that would be used for waiting on the said events. What have you thought of to solve this? “Follow your bliss.” – Joseph Campbell

Your requirement sounds far too suspicious for anyone to help. जय हिंद

Next time, copy and paste the code. Don't retype it from memory. You'll get the order of statements wrong and quite possibly not convey some minor detail that makes all the difference to whether your code runs or not. Between the call to .Start and .WaitForExit, add the line p.WaitForInputIdle(). This will force your code to wait for the app to start. A guide to posting questions on CodeProject[^] Dave Kreskowiak Microsoft MVP Visual Developer - Visual Basic      2006, 2007, 2008

Create your own Desktop-object[^] :) I are troll :)

The OpenFileDialog class is a wrapper to call the Win32 function OpenFile (? I can't remember which the function name exactly!). Win32 displays the dialog, not the .NET class OpenFileDialog. OpenFileDialog is also a sealed (NotInheritable) class, so you can't really modify it at all. You can't even get the window handle to the dialog and start throwing messages at it since your code stops running when you call the dialogs .ShowDialog method. Your going to have to write your own dialog to support this. It would just be a simple Form with a TreeView for a directory browser, and a ListView for files in the currently selected directory. Oh, and of course, a couple of buttons for Open and Cancel. A guide to posting questions on CodeProject[^] Dave Kreskowiak Microsoft MVP Visual Developer - Visual Basic      2006, 2007, 2008