vb.net help!

[mayati]

I am programing in vb.net and having sql server 2000 as database. I have two questions:
1- How to connect dynamically to the server from a vb.net form field by the user(user enters server, database, username and password)so this connection will be available for the rest of the forms in the application.

2- I have to migrate millions of documents and their related data from one sql 2000 server to the other. I have retrieved from the source database into data readers and now I have to migrate it using ready implemented web services, what I have to do is when I start migration I have to have a pause/resume functionality so if user wants to pause after few thousands document and then resume to continue. I am lost and do not how to do this. Help please!

[Enyi]

I am programing in vb.net and having sql server 2000 as database. I have two questions:
1- How to connect dynamically to the server from a vb.net form field by the user(user enters server, database, username and password)so this connection will be available for the rest of the forms in the application.

2- I have to migrate millions of documents and their related data from one sql 2000 server to the other. I have retrieved from the source database into data readers and now I have to migrate it using ready implemented web services, what I have to do is when I start migration I have to have a pause/resume functionality so if user wants to pause after few thousands document and then resume to continue. I am lost and do not how to do this. Help please!

1)
Somewhere you probably would have an sql connection object right? Wherever you declared this would decide where it can be accessed from (other forms, classes etc). To get text boxes values into would go a bit like...

Dim sqlConn as New SqlConnection("Data Source=" & txtServer.Text & "; Initial Catalog=" & txtDatabase.Text & "; User Id=" & txtUsername.Text & "; Password=" & txtPassword & "")

Got to make sure all the quotes and &'s are in the right place, this can get confusing.

As for number 2, I would get lost as well

[mayati]

Hello Enyi,
Thank you for your concern, do you think threading will be a good solution for my number 2 question

[mayati]

Hello again Enyi,
sorry I forgot to ask you about your reply to my question nr 1. Now I have the declaration, where I should declare it to be able to use it theroug the project, so I do not need to declare it in every single form.

[Enyi]

Hello again Enyi,
sorry I forgot to ask you about your reply to my question nr 1. Now I have the declaration, where I should declare it to be able to use it theroug the project, so I do not need to declare it in every single form.

Well, you'll probably store it in a class or module maybe? I'm currently a beginner in programming in general, so sorry if im a bit vague. I think a module would be good. But I've only used them once, so im not exactly sure what they are used for.

Sorry, that's all about I can give. I remember having to do some VB.NET for a college class 6 months ago, I hated trying to pass variables through to forms, and back again. That's where I got the idea of the module from, but I can't remember much about that now.

As for threading, umm, do threads die when the program is closed? and can they be paused and resumed? :confused:

[sashi]

Hi guys,

scope of the variable is to be considered when it comes to declaring variable.. i.e. Global, Module, Local..

Understanding Variable Scope and Duration
There are two key attributes of all variables in Visual Basic that are essential to understanding their use:

Scope
Scope defines the visibility of a variable. Variables can have scope ranging from global where any procedure in the application can access the variable to local to a single procedure.

Duration
Duration defines the lifetime of a variable. Variables can exist for the life of an application or can be created and destroyed in a single procedure.

Global Scope
Global variables are available anywhere in your program. Any line of code in any procedure can read or write the value of the variable. While convenient, it is considered bad programming practice to overuse global variables and some programmers (myself included) make a considerable effort to avoid them entirely.
To create a global variable, declare it in the declarations section of a standard module using the Global or Public keyword.

Module Scope
Module level variables are available to any code within the module where they are declared. While using global variables is considered bad programming practice, using module level variables is not. Module level variables allow you to share data between procedures without exposing that data to every procedure in the application.
To create a module level variable, declare it in the declarations section of a module using either the Dim or Private keyword.

Local Scope
Local variables are only available to the procedure in which they are created. Local variables are the most restricted in scope - not even other procedures in the same module may read or modify local variables.
You create local variables by declaring them with the Dim or Static keyword within the body of a Sub, Function, or Property procedure.

[Swrnl]

Hi,

I've created a module (.bas) file in ASP.NET and created some properties. I'm setting those properties values in page load event. When I see the module properties, they show NULL. What is the scope of the module variables and how they can be used in ASP.NET