Sorry Gjm, my mistake. Put the app_data directory into your production environment.

Have you deployed the app_code directory to your production environment? This is where the membership datebase is stored. Alternatively you can create the database in SqlServer like this: http://msdn.microsoft.com/en-us/library/x28wfk74.aspx[^] Which will let you store users in a proper database. If you go down this route make sure you change your web.config to point to the external DB.

It's going to be difficult to test without an actual web service to test against. Is it a commercial service? If so they should have a test service for you to code against? If not you could create a mock webservice of your own. You know the methods and return types from the wsdl so you could code against that.

lukasz_nowakowski wrote:

And personally I consider first form more readable.

I agree, String.Format is more readable, especially when you have a few more arguments.

You do need the URL yes but you could host it locally for testing. Rather than use the command line, it might be easier for you to just add a Web Reference to the .net project directly. This will create your proxy class and add the URL of the webservice to your web.config. That way you can change this to a production server on release. This is explained here: http://msdn.microsoft.com/en-us/library/ms169816.aspx

Is your local firewall blocking port 2076? If you run the site on your local IIS server, the default port is 80 which again you'll need to make sure isn't blocked by your firewall.

This article should point you in the right direction. generating-asp-net-images-fly Ignore the parts about generating the image but if you look at Response.ContentType and the way to link to the image this should let you create an aspx page in which you can save request details to a database and then send your image to the client browser.

You could allow your clients to FTP the files to you and then process them with a dedicated application rather than through the web application?

Your page_load event will get called each time there is a postback. So when you click your save button it's setting your flag back to -1. you should look at:

page.isPostBack

If you are opening the excel file using a filestream you could use the fileshare parameter to prevent any other users from reading the file.

You could try this: http://msdn.microsoft.com/en-us/library/system.data.dataset.merge(v=VS.71).aspx[^]

OK, so is the report a datagrid bound to the dataset created by this query? Why don't you try something like this: Create a view of your main query which returns all possible columns you might want to display on the report. Then in your stored procedure have a parameter for each column you might want to filter on.

@col1 varchar(50) = null,
@col2 int = null,
@col3 bit = null

SELECT col1, col2, coln
FROM view1
WHERE 1 = 1
AND isNull(@col1, col1) = col1
AND isNull(@col2, col2) = col2
AND isNull(@col3, col3) = col3

Then depending on what the user has requested by drilling down, show/hide columns in the datagrid and pass in only the parameters that you want in the where clause. The isNull() will ignore any parameters you pass in as null and so won't take effect. If you want OR's you could run the procedure multiple times and join the datasets that are returned.

Hi, I sort of see what you're trying to do here but I think there are neater ways. You're not really going to get the benefits of stored procedures but building up your sql like this and it's going to be very difficult to maintain. I think you're trying to get one procedure to cater for all possible data access that you might want at any point in your application. How many different combinations of data do you need from exactly these tables? I'd recommend splitting this procedure into several more specific procedures and then calling the procedures with strongly typed parameters. Or if you're building a much bigger system try reading up on ORM. If you want to post a typical query that you might need from this database I can have a look at reformatting it for you.

It's probably not ideal to be dynamically generating WHERE clauses and passing the to your procedures. Could you post the Stored Proc code as there might be an easier way round this?

Word press is written in PHP, I don't think you'll be able to easily integrate it into your asp.net app. There are plenty of other blogs you could use that are implemented in asp.net.

Do you mean you want to save an Etudiant to the DB or you want to populate an Etudiant from the DB?

The local DB will probably be mySql and the remote will be Sql Server so I don't think that would work. Also the data is not replicated as such, it's used to alter the data in the remote db. I should also say that this transfer will occur pretty regularly but not at time defined intervals. So what I'm thinking is that there would be a local app to get data from the local db and to send it to a remote webservice which would use that information to update the remote db unless there is a faster way to do it? Is remoting likely to be faster? Thanks, Rhys

I have some vague requirements at the moment but basically I need to take some data from a local database and use it to update the data in a remote database. The local application does not have direct access to the remote db. Because of the nature of the business, this data update needs to be a fast as possible. My first instinct would be to put up a webservice on the remote server and use this to update the remote database but does anyone know of a way that would be significatly quicker? Thanks very much

Could you post your code please?

You could check your database to see if a record with all the information has already been inserted.