Distributing Database applications

[David]

I have been going around in circles trying to understand the method of
creating a database in VB.Net 2003 and distributing that application and
database.

It seems if I use the Server Explorer to create the pledbConnection etc, the
link to the database works ok on the local machine but when the application
is distributed, the program points to the original path (which of course is
different to the target system). Is there any way to maintain the releative
path to the database when you distribute the application.

Secondly, the tutorials I have point heavily to using a SQL server instead
of oledB . I found MSDE 2000 and downloaded it but cannot install it. The
dialog indicates it needs a strong SA password and I am not sure what this
is and how to apply it.

Also, if I eventually managed to install MSDE, can it be installed with the
application or does the user needs to install this separately ?

Thanks in advance.

[chanmmn]

Of course it can be automated by those I call them wrapper like Install
Shield and so. But just install your MSDE saprarate will have no harm. Learn
isql at command prompt sometime could be useful for you. Good luck.

chanmm

"David" <da***@orbitcoms.com> wrote in message
news:VJ******************@news-server.bigpond.net.au...

I have been going around in circles trying to understand the method of
creating a database in VB.Net 2003 and distributing that application and
database.

It seems if I use the Server Explorer to create the pledbConnection etc, the link to the database works ok on the local machine but when the application is distributed, the program points to the original path (which of course is different to the target system). Is there any way to maintain the releative path to the database when you distribute the application.

Secondly, the tutorials I have point heavily to using a SQL server instead
of oledB . I found MSDE 2000 and downloaded it but cannot install it. The
dialog indicates it needs a strong SA password and I am not sure what this is and how to apply it.

Also, if I eventually managed to install MSDE, can it be installed with the application or does the user needs to install this separately ?

Thanks in advance.

[DM McGowan II]

"David" <da***@orbitcoms.com> wrote in message
news:VJ******************@news-server.bigpond.net.au...

I have been going around in circles trying to understand the method of
creating a database in VB.Net 2003 and distributing that application and
database.

It seems if I use the Server Explorer to create the pledbConnection etc, the link to the database works ok on the local machine but when the application is distributed, the program points to the original path (which of course is different to the target system). Is there any way to maintain the releative path to the database when you distribute the application.

Secondly, the tutorials I have point heavily to using a SQL server instead
of oledB . I found MSDE 2000 and downloaded it but cannot install it. The
dialog indicates it needs a strong SA password and I am not sure what this is and how to apply it.

Also, if I eventually managed to install MSDE, can it be installed with the application or does the user needs to install this separately ?

Thanks in advance.

Ask in the ADO.NET newsgroup for a wider database oriented audience and
their responses.

For MSDE, search Google for "msde sapwd setup". Don't install it with a
blank password.