Arch4ngel

Here is what I found after 5min of Google Search: http://www.bobpowell.net/generating_multipage_tiffs.htm

Okay... if your "application" is a website... I say ASP.NET Application. If you want a normal window... I say Form. But after that... you can choose if you are going with VB.NET or C#. You also might want to take a look at the System.Data.SqlClient namespace. Much needed for what you want to do. But.. obviously... you didn't gave us that much info to help you and this is what we can tell you for what we had.

That lead you back to linking your code to Microsoft non-managed DLL. You might get information on how to do it through: http://www.codeproject.com/vb/net/ClickThroughWindows.asp?df=100&forumid=262268&exp=0&select=1356584 http://msdn.microsoft.com/library/default.asp?url=/library/en-us/winui/winui/windowsuserinterface/windowing/windows/windowreference/windowmessages/wm_move.asp But never did it personally. You might want to take a look at WM_Moving too. Here you go.

OKay sorry for all those quick replies but here is a few links that might interest you: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnvs05/html/codesnippets.asp http://gotcodesnippets.com/default.aspx

Does your question look like this one? http://geekswithblogs.net/kakaiya/archive/2005/06/17/43957.aspx If yes... I'll do my research on that and will come back to you on this.

Remind me of my own homework when I was on my professional class lol

Found it at google 2 years ago. Left for a year and now I'm back with the thousand post coming close (even though at the moment you read this comment I might be higher... dynamic word you know...) And I really think a technical society like that is really needed to keep some vital information alive and available for everyone. Cheers

Dont know what you are trying to do... but you are trying to convert an HTTP stream into a picture. The link that you are building is a link to an HTML page. Not a picture. You might take a look through the API http://www.google.com/apis/maps/

I'll need to see your code because when I use interfaces in C#, they dont allow me to have variables, initialization or code within properties or methods.

If you build your interface with C#, you can use the XML comment that are actually built within the DLL. (/// thing) You'll be able to add remark and description of every parameters. If you are using VB.NET... it can only be done with .NET 2.0 (find it stupid). And last... no... you can't have interfaces with code within them. Interface is like a blueprint that people must follow. There is virual class that allow you to have partial code in there (much more like a incomplete class). So that's it. If you have any other questions, feel free to ask!

Okay... here is my piece of advice. I'm a C#/VB.NET programmer. I do Web/Desktop development and I'm pretty happy with the RAD I have now. However... I know that the .NET framework is still not "the way to go" with non-Microsoft OS. So... learning .NET platform was only for Microsoft-using customer. Good or bad choice? Dunno... but there is one thing that is still getting on my nerve today... I don't know C++. I want to learn it. I know that this language going to be compatible with Linux/Windows. The only thing that might change in between is the libraries. You see? Since C++ is CLI compliant, you have an edge over me. I'm saying... learn the C++/CLI "proper way" and extrapolate exemples found in C#. You'll find yourself with more exemples than you can handle. And for C++ .NET tutorial... take a look there: http://www.functionx.com/vcnet/index.htm I would say to keep with C++ since you it's going to be needed for a long time and you can always convert your code to .NET. And while you process this quick conversion... you can always learn C# and take your time. Cheers

I'd use the System.IO.Directory because of it's was built to do the job. It's not faster or slower but you can handle exception and benefit from all the methods that have been included inside of it. Cheers

And if you install XP Home, watch out for ASP.NET because it doesn't come with IIS and make sure you are not on a domain because XP Home can't join a domain, etc.. etc... Can't understand why though. Need to pay 100$ more for this? humm... quite interesting. Cheers

Complex problem/ Simple Solution. Instead of having 2 submit... keep only 1. Put a radiobutton to let the user fill the right section. Base yourself upon that radio button to process either one of those. This is it :) The KISS again :) (Keep It Simple Stupid)

You might want to take a look at that link: http://www.connectionstrings.com/ But here is the syntax: Standard Sybase System 12 (or 12.5) Enterprise Open Client: "Driver={SYBASE ASE ODBC Driver};Srvr=Aron1;Uid=username;Pwd=password" Of course... you use the ODBC objects from System.Data.Odbc and you should be fine doing a lot of nice stuff :)