Yes. If only closed minds would come with closed mouths. Ego non sum semper iustus tamen Ego sum nunquam nefas!

Leon v Wyk wrote: //e.StoragePosistion this.BeginInvoke( new NewSMSReceived( this.OnNewSMSReceived) ); This becomes (I removed all the 'this.', I find it weird): Invoke(new MethodInvoker(OnNewSMSReceived), new object[] { your variables go here }); Other alternative would be using properties, since you're on different threads, but will be invoking methods on the same object ('this.'). Yes, even I am blogging now!

Use the GDI+ GetPixel method

Doing them in a set wont speed anything up more for you. Best is to perhaps export the table to a temporary access database, zip the file , send it to other side, etc ,etc. Access tends to compress very well. Leon v Wyk wrote: at the moment I Export the records one by one and delete the records as I go along. This is very slow...I am dealing with 1000s of records :laugh: I can picture that :rolleyes: leppie::AllocCPArticle(Generic DFA State Machine for .NET);

This is a fairly old thread, but I just stumbled across it looking for an answer to a distributed transaction question I have. Anyway, does your export procedure need to be transactional? i.e. Do you want to ONLY delete the source records once they are in the remote system? And do you want the destination records to ONLY be valid once they are deleted from the source? I have architected many systems like this where the data needs to be in one place OR the the other but not both, and not get lost, like in this example. while (there are more records to export) { begin transaction; try { export record to remote system; delete record from local system; commit; } catch () { rollback; } } These systems are hard to accomplish, sometimes you are better off assuming that the 2 systems are only going to communicate asychronously and then revisit the problem you are trying to solve. If that doesn't help you one iota I won't be too suprised. JBoy

In order to find out the number of records in a database table "table", use the SQL Command: Select count(*) from table In general, try to get familiar with SQL and what it can do for you. It can do a LOT more than procedural code.