OK, I am most certainly no expert with VB.net, but what VB.net development I have done over the last 2 years in VS2008 & VS2010 might offer some suggestions for you.
First, get the appropriate connection string information you need from:
Obviously that info is 'genericized' so it will need to be customized to your own requirements.
Note - you can test the connection string via a UDL file
Then you can find how to use the Connection string in your code.
Next, within Visual Studio I'd layout the user forms/pages (the ...aspx files) - setting the needed objects to
runat="server"
Then in the form's ...aspx.vb file I'd develop the code to do what was needed.
In the
Sub Page_Load() method I'd have a
If Not (Page.IsPostBack) Then....Endif section I'd have code to populate the mentioned Combobox with the Access data table filenames.
This can be done by 'hard-code' or by having the system 'read' the associated directory and populate the Combobox with what it finds.
Now the user can make the needed Access filename selection.
Since you don't want the server to have to work each time the Combobox selection changes (such as scrolling through the values), you might want the next action to occur on the click of some button.
When that button is clicked, the
Sub button_Click() would be accessed which would acquire (via and ODBC Connection) the requested data and display it into a DataGrid on the form/page.
You don't say how the
User selects their Excel template.
* Do they have this in another Combobox?
* Or is it presented to the user in some other manner?
Regardless, you would do something similar to the above to acquire the Excel data.
You also do not go into detail on
The system will look at the Microsoft Access table data vs. The Excel Uploaded Data
* Is the 'system' somehow doing some 'comparison' of the data - row-by-row, field-by-field?
* Or is the user comparing the data?
* Or what?
And then, under what circumstances, will it write out the data to another Excel file?
Obviously there are a LOT of things that need to occur.
I'd start with just setting up the user form/page and getting the most simple things done (maybe read the Access file and display the data).
After that was working, I'd go on to the next part of the problem - going piece-by-piece until all the parts were complete.
Keep in mind - the value of what I offer is proportional to what you had to pay for it.
Good Luck,
JRB-Bldr