Explanations

I began to develop a system for a club in VB 6 with Access in the year of
2002. It is even last year I was finishing implementing the dozens of
modules for several departments.
The subject is that I intend to change everything for .NET, C #+ SQL Server
2000 for being more specific.
Now see my problems:
- I am using they DAO;
- Transaction with Access is terrible, I had several problems (I think nor
needs to talk about the problems);
- 4 bases (MDBs) different;
Now I have a main software in the Freedom-SP with a called MDB
NCCLiberdade.mdb. the whole cadaster of partners and control and position of
payments is centralized in this MDB.
Already in the club in Aruj-SP 3 different banks exist:
club in Aruj and they are not necessary in the office of the Freedom.
Tennis of Field, Volleyball, Soccer, etc.
Field.
The whole Friday I put upon the file NCCLiberdade.mdb in Aruj
so that we can have an updated position of who paid for the bank during the
w in the Freedom.
Now the subject is, as it will be that I do for that to migrate for SQL
Server, because I work with several bases. And how Backup of the data of the
Freedom would be for Aruj.Wow, you developed it for over two years and now you want to scrap it and
rewrite it? Have fun!
It sounds like your four different databases could live within one single
database in SQL Server. This will make maintenance (e.g. Backups) much more
manageable, and much more transactionally consistent, than they currently
are in separate files using Access.
And no, you don't have to defend your choice here... Not many Access
advocates are going to groan about you upgrading. :-)
On 3/14/05 7:36 PM, in article u0InCYPKFHA.576@.TK2MSFTNGP15.phx.gbl, "Frank
Dulk" <fdulk@.bol.com.br> wrote:

> I began to develop a system for a club in VB 6 with Access in the year of
> 2002. It is even last year I was finishing implementing the dozens of
> modules for several departments.
>
> The subject is that I intend to change everything for .NET, C #+ SQL Serve
r
> 2000 for being more specific.
>
> Now see my problems:
> - I am using they DAO;
> - Transaction with Access is terrible, I had several problems (I think nor
> needs to talk about the problems);
> - 4 bases (MDBs) different;
> Now I have a main software in the Freedom-SP with a called MDB
> NCCLiberdade.mdb. the whole cadaster of partners and control and position
of
> payments is centralized in this MDB.
> Already in the club in Aruj-SP 3 different banks exist:
>
> club in Aruj and they are not necessary in the office of the Freedom.
>
> Tennis of Field, Volleyball, Soccer, etc.
>
> Field.
> The whole Friday I put upon the file NCCLiberdade.mdb in Aruj
> so that we can have an updated position of who paid for the bank during th
e
> w in the Freedom.
>
> Now the subject is, as it will be that I do for that to migrate for SQL
> Server, because I work with several bases. And how Backup of the data of t
he
> Freedom would be for Aruj.
>
>
>|||"Frank Dulk" <fdulk@.bol.com.br> wrote in message
news:u0InCYPKFHA.576@.TK2MSFTNGP15.phx.gbl...
>I began to develop a system for a club in VB 6 with Access in the year of
> 2002. It is even last year I was finishing implementing the dozens of
> modules for several departments.
>
> The subject is that I intend to change everything for .NET, C #+ SQL
> Server
> 2000 for being more specific.
>
> Now see my problems:
> - I am using they DAO;
There are better database facilities in .NET - System.Data.SqlClient
specifically.

> - Transaction with Access is terrible, I had several problems (I think nor
> needs to talk about the problems);
>
SQL Server will treat you much better.

> - 4 bases (MDBs) different;
SQL Server will allow you to set up and manage several databases on one
server.
<<snip>>

> Now the subject is, as it will be that I do for that to migrate for SQL
> Server, because I work with several bases. And how Backup of the data of
> the
> Freedom would be for Aruj.
First, before you do anything with the migration, make sure you have backups
of your Access MDB files! Can't stress that enough!!! You know to backup
an Access database, just copy the MDB file and burn it to CD/DVD or back it
up to a tape drive.
Next, Access has a built in SQL Upsizing Wizard. Just run it on your MDB
file and follow the prompts. When you get done, you will probably want to
tweak your SQL database a little, for performance, but the Upsizing Wizard
does most of the dirty work for you.|||If you were developing on Access, wouldn't you? Hehe. Good point about
combining everything into one database. However, make sure that you don't
have tables with the same names in each database. If so you'll have to
modify your program or keep them in separate databases.
"Aaron [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
news:BE5B9BAA.3230%ten.xoc@.dnartreb.noraa...
> Wow, you developed it for over two years and now you want to scrap it and
> rewrite it? Have fun!
> It sounds like your four different databases could live within one single
> database in SQL Server. This will make maintenance (e.g. Backups) much
> more
> manageable, and much more transactionally consistent, than they currently
> are in separate files using Access.
> And no, you don't have to defend your choice here... Not many Access
> advocates are going to groan about you upgrading. :-)
>
> On 3/14/05 7:36 PM, in article u0InCYPKFHA.576@.TK2MSFTNGP15.phx.gbl,
> "Frank
> Dulk" <fdulk@.bol.com.br> wrote:
>
>|||> Next, Access has a built in SQL Upsizing Wizard. Just run it on your MDB
> file and follow the prompts. When you get done, you will probably want to
> tweak your SQL database a little, for performance, but the Upsizing Wizard
> does most of the dirty work for you.
It does some dirty work all right!|||Nothing that can't be cleaned up with a little Pine-Sol and a green scrubby
pad :)
"Aaron [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
news:BE5BBFC1.33D0%ten.xoc@.dnartreb.noraa...
> It does some dirty work all right!
>