Results 1 to 5 of 5

Thread: Re: Multi-User version of my VB project

  1. #1

    Thread Starter
    Lively Member
    Join Date
    Oct 2000
    Posts
    80

    Wink

    I am currently designing a database program in VB 6.0 SP4 Enterprise edition. I am using ADO 2.5 for my Access database. My question is, I hope, very simple.

    I am going to have a single user and a multi-user version of this program. For the multi-user, do I use SQL Server to host the .mdb files? I plan on having anywhere from 2-15 users on the system at the same time. There probably will be around 8-10 different .mdb files when I am finished.

    Also, how much do the server programs that you recommend cost?

    Thanks,

    Eric

  2. #2
    Frenzied Member
    Join Date
    Aug 2000
    Posts
    1,539
    sql server doesnt run .mdb
    its a giant server that you can have many databases in

    one .mdb file is ONE database
    if you set up a sql server, you can have multiple databases
    dont use mdb's
    get sql server..
    .mdb files are MS Access only

  3. #3

    Thread Starter
    Lively Member
    Join Date
    Oct 2000
    Posts
    80

    Exclamation

    To use a SQL database, I am assuming I would have to by SQL Server?

    Can you point me in the right direction to get starting making a SQL database? Can I make a database and develop it in a single user environment and then get the server later down the road?

    Thanks, and sorry for the very newbie questions 8-)

    Eric

  4. #4
    Fanatic Member
    Join Date
    Oct 2000
    Location
    London
    Posts
    1,008

    Multi user

    Access will support multi user use. SQL Server is a whole different kettle of fish.

    It entirely depends on the levels of security and assurance you need. SQL Server is *relatively* expensive and runs as a service under Windows NT. Unless you have knowledge of NT and SQL Server, you need some outside help.

    Access is an end-user database designed for rapid deployment and low cost. Its security model is weak and its logging is non-existent. It works well for, say, less than 250,000 records but if the data structures are complex, you can easily run into problems with queries etc.

    SQL Server provides a whole new level of security and transactional protection but it is a BIG topic. If you are not comfortable with Database Design topics, I would steer clear.

    If you want a consultant and pay good rates - that is a different matter *chuckle*

    Hope that is a bit clearer,

    Paul.
    Not nearly so tired now...

    Haven't been around much so be gentle...

  5. #5

    Thread Starter
    Lively Member
    Join Date
    Oct 2000
    Posts
    80

    Lightbulb

    Thanks for the info. It is becoming more clear :-)

    It sounds like Access database files will work just fine for what I am doing. I don't plan on having anywhere near 250,000 records, security is not a highly prioritized issue, and the database structure is not that complicated.

    My only question that remains is how do you share the access database files across a network? Do you need any type of server program or do you just place them in one location and then tell my program, which is on multiple computers, to go to that database file?

    Thanks again...

    Eric


Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  



Click Here to Expand Forum to Full Width