PlausiblyDamp

If possible could you attach the source to the projects - it might be easier to see what is going on with more code to look at.

Try using just union ratherthan union all

myDataView.RowFilter = "Country = '" + arg + "'";

Does the class objPlugin is set to implement the IPlugin interface? Also wher eis the IPlugin interface defined (in a shared library etc)?

If you step through the code does the CreateInstance method inside the DLL work every step of the way? If not which line within the DLL fails (probably on assembly.CreateInstance). What is the value of _parser when you run the above code? Does it contain the name of a valid class?

Any chance you could post the relevant code? It makes it a lot easier for people to help if they don't have to imagine the source....

You probably want to create your own database rather than just adding tables to master. Also the ASPNET account (the account asp.net web aaplications run under) will need to be given permissions to access the database in question.

Private _colour As System.Drawing.Color = System.Drawing.Color.Red

If you are moving from VB6 then most of the changes are for the better, however if you so desire you can turn off Option Explicit (although this is only going to introduce the oportunity for bugs so why would you), continue to use the VB6 style of arrays, VB6 string handling etc. Earlier you mentioned print has gone from the language, printing direct to the VB6 form rarely give a decent output and most definately didn't produce professional output. If you relied on the mscomm control then there is a rs232 wrapper on MS's site that does pretty much the same thing but gives you more control and more capabilities to extend the functionality. Moving to a more OO style give much more long term benefits in terms of reuse, maintainability and architectural design choices, some of these changes have required a fairly fundamental restructuring of VB. As well as one or two old favorites being cut though many, many old annoyances have gone as well (COM & the registry, poor file handling, COM and memory management, lack of registry support, lack of networking support, poor error handling spring instantly to mind). As to the comment about because it is a lot harder then .Net ;)

In your connection string the is probably wrong, rather than the table name replace Term with the Database name.

IIRC you set the reports record source property to the dataset / datatable

Like I said in the other thread, a web server cannot access files on a client's machine. The .FileName property will give you the path of the file on the client - this can be useful if you need to store the posted file somewhere on the web server and wish to give it a name, but it will not allow the server to access the file on the client.

Whatever the user enters in the grid will be assigned to the variable _Title - not sure what you mean by

http://www.xtremedotnettalk.com/showthread.php?t=91067

http://www.xtremedotnettalk.com/search.php?searchid=121141

Try using a parameterised query rather than concatenating strings to build your SQL.

There is no way for a server side asp.net application to directly access the client's HD to either read a file or discover it's location. If you are using the HtmlInputFile control then on the server side you will need to use it's PostedFile property to read the file the browser has uploaded. Given the following asp.net code </pre><form id="Form1" method="post" runat="server"> Text="Button"> </for You should be able to read the files contents with code similar to Dim sr As New System.IO.StreamReader(File1.PostedFile.InputStream) 'can read from file using standard io commands now 'e.g. Dim s As String = sr.ReadLine()

any chance of giving us the error message / number that is returned? Also VS 2005 is Beta software, it will have bugs and there are going to be problems attempting to use it.

What version of VS did you have on before? It sounds like you solution files were created in 2003 and you have re-installed the 2002 version.

Try enclosing the dates inside # rather than single quotes. Or alternatively try using a parameterised query.

IIRC you need to enclose dates inside # characters.

Have you tried using the DataView's Rowfilter property and use an IN clause for the criteria?

Have you also referenced the System.web.dll? If so it should be there.

Depends on the type of information being returned really. If it is several 'results' to a function call where each value is the same data type and there is no relationship between the values then an array may be best. e.g. String.Split(...) If the two values have an intrinsic relationship (StartTime / StopTime, InitialBalance / NewBalance) then I would tend to create a class / struct to contain the values e.g. Point, Size etc.