Visual Basic

The general rule is yes, of course. Objects that expose the IDisposable interface do so because they contain resources that a limited in some way. The destructor/finaliser of these objects will call Dispose anyway, but is it better to call Dispose when you know you don't need the object any more. Why? Because you don't know when the garbage collector will clean up after you, which could mean that you run out of the resource and are then left wondering why your program failed. So... If its got an IDisposable interface then use it. --Colin Mackay-- "In the confrontation between the stream and the rock, the stream always wins - not through strength but perseverance." (H. Jackson Brown)

You must have an SMTP server _somewhere_ if you are mailing to the internet in general; internet mail requires it. [There are some localized mail systems that don't use SMTP.] However, you don't need a _local_ server. If you can access internet sites directly, you can do the send from a local process to the remote site directly. To do this properly you _MUST_ understand the relevant internet standards. Basically, however, you need one of the many .NET components that can send mail using MX lookup, rather than only forwarding it to a proper SMTP server. HTH, Ruth

In that case, you might want to start here[^]! RageInTheMachine9532

If it does, it's very well hidden! Best bet looks like API again. :-D RageInTheMachine9532

OK. In that case, you should be using a RecordSet object to track the data in your app. Next, you didn't mention how you were generating your report, so I'll assume your writing the code for it yourself. Now, you'd have to print the data out, something like this (assuming 50 rows per column): Rec(0).Field1 Rec(0).Field2 Rec(0).Field3 : Rec(50).Field1 Rec(50).Field2 Rec(50).Field3 Rec(1).Field1 Rec(1).Field2 Rec(1).Field3 : Rec(51).Field1 Rec(51).Field2 Rec(51).Field3 A simplified view of the code might look something like this (not actual code): Dim Index as Integer Dim rsData as RecordSet (Your data is in here) Dim strOutput as String 'Output your headers here ' For Index = 0 to rsData.Count - 1 strOutput = rsData(Index).Fields(1).ToString & " " & _ rsData(Index).Fields(2).ToString & " " & _ rsData(Index).Fields(3).ToString Try strOutput = strOutput & " : " & \_ rsData(Index + 50).Fields(1).ToString & " " & \_ rsData(Index + 50).Fields(2).ToString & " " & \_ rsData(Index + 50).Fields(3).ToString Catch End Try Print strOuput Next Again, this is a greatly simplified example and will NOT compile! But it should be enough to give you an idea of what is going on. RageInTheMachine9532

You can't use the code directly. You'd have to either rewrite it in VB.NET or compile it directly into a .DLL and use it that way. The other option is to look for other high resolution timer controls such as the CCRP High Performance Timer Object, which can be found here[^]. RageInTheMachine9532

OK. In that case, your best bet is to have your app check the command line parameters, probably in the form load event. That way, you can have the greatest flexibility as far as interface with various scripting languages or other applications you may write for the front end of the project. Now, you might also want to consider writing your app as a component (aka control). That way, you still have the flexibility of using your component in other scripting and app projects and you also get the added bonus of return values and greater flexibility of error traping and control in your front end app/script. RageInTheMachine9532

Thannnnnkkkkkk men.. the MDAC installation was the problem... waooooooo.... that's great.. Johnny

thanks mate the numbers are in a listbox not a textbox

Thanks I will have a read Thanks A lot vbnetuk@yahoo.co.uk

Brooksy wrote: Any guidance to get us started will be appreciated. First, I've never heard of the MCI patent and I've been working with Telephony for the last 4 years developing similiar systems, but then I'm a developer now a lawyer. What you describe is basically an IVR system (Interactive Voice Response). A lot depends on what you have answering the call. I assume it is a proper phone PABX rather than a modem? Knowing the hardware will allow you to define your software requirements. Most decent phone systems will already have an IVR that you can purchase which will do what you require. Some phone systems support TAPI, others have their own API's. So the first step is to identify the hardware that is answering the calls. Michael Blue canary in the outlet by the light switch Who watches over you Make a little birdhouse in your soul - They Might Be Giants

See this reply[^]. :) RageInTheMachine9532

You can't use .NET Framework classes directly in VB6, but you can use classes and components that you write. So, you'll have to write wrappers around anything you want to use, register the Assembly and create a Type Library for it. For an example of this see this example on MSDN[^]. RageInTheMachine9532

I ran into the same problem with IE and getting the script errors. I did EVERYTHING to try and get the thing fixed, including reinstalling Windows 2000, the Service Packs, patches, upgrading IE, Windows Scripting Host, ..., I mean EVERYTHING! ... and it didn't work... The ultimate solution was to reinstall the machine from scratch. Kill the partition off and start over... That Sucked! :) RageInTheMachine9532