One word of warning with this technique, the following give different results: 859 / 5 * 1.0 1.0 * 859 / 5 If you go down this route, you will need to understand how SQL Server applies its rules for implicit datatype conversion.

We did not use any automated tools. In our case the way you do things in .net is different enough that it was probably a good idea to re-write the existing delphi code to better match the new .net structure. I have looked for that document, it looks like I didn't take a copy of it when I left my previous employer. It was a good experience to move to .net. Some of the issues we were facing were a lack of people we could hire that had delphi skills. The reality is that there are far more .net programmers out there then delphi. Now that I have been doing .net for 5 or so years, I wouldn't go back to delphi either. I really liked delphi as a product, but it tends to be a little behind the microsoft release. I still remember about 10 years ago where we had to wait almost a year before we could use ado in delphi. Now that delphi has .net that could always perhaps be an option too. Again you don't have a lot of people that will say they know delphi .net The company I worked for went with vb.net and left delphi behind. I havn't worked there in 2 years, but I would guess most of their delphi code is gone. The .net framework is great, I think it would be a good move to get on .net Hope that helps. Ben

You can't. There's no way you can just "connect" to a remote COM port like that. You have to have a remote application running on the target machine to use that machines COM port, then you establish a connection between your local app and the remote app over the network using any method you want, like .NET Remoting, WinSock, ... Dave Kreskowiak Microsoft MVP - Visual Basic

There are two types of constant values, constants and read-only members. You have to decide what type you want to use. Constants are compiled into the code, so if you use a constant from a different project, and then change the constant in that project, you have to recompile the code that uses the constant in order for it to change there too. Read-only members are read from the source every time, so if you change the value, it's guaranteed to change everywhere it's used. Also, a read-only member can get it's value from an external source like AppSettings. If the external source is expensive to read (like a file or a web service), you can read it the first time it's used and cache it in a local variable. I usually create a static class called Settings where I put application wide constants and settings. It will contain constants and read-only static properties. --- Year happy = new Year(2007);

Well, I did mean TableAdapters - the new thing introduced with VS 2005 (not a part of .Net 2.0) The mapping of fields and columns with the properties is the most natural mapping IMHO and the App Logic layer would have that ultimately in one form or another. My question is - what is the better approach between such mapping and TableAdapters. Shreekar

Thanks a lot!!! I guess I was looking at the code too hard...:doh: But there is something nagging me at the back of my mind.:confused: I think I will test more and respond. Thanks again. Shreekar

You're welcome, and I would like to hear how you did. My advice is free, and you may get what you paid for.

There is an example based on SQL Server at http://www.programmingknowledge.com/ImageUpload.aspx[^]. You will need to do some changes to work with Access Database. Good Luck

Everything I post here is in the public domain, and its use is allowed in any context. In other words, have at it. :) "Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997 ----- "...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001