Kevin,

No matter which way you end up doing it, keep in mind that the way to make this the most flexible is to do all your data access in a separate class. Don't put data access code in your UI classes.

~~Bonnie


>Well everyone,
>
>I've gotten to different answers on this;
>
>Open the connection and keep it open, and open the
>connection when you need it, then close it.
>
>As I said in an earlier post, I dont expect to use
>this app across the web anytime soon. It is primarily
>a desktop app, which might later access the data on a LAN.
>
>So I guess I will open the connection and leave it open.
>I could always change that later.
>
>Thanks for all the input!
>
>
>>In a .Net application, do I want to create a connection
>>on application startup, or only when I'm ready to access
>>the data?
>>
>>Thanks