Describe the advantages and challenges of using a team to develop a Access database.?
605942
I think there are more challenges than advantages in this situation.  First of all, if you all don't have the same naming conventions you are screwed right off the bat.  Secondly, how are you going to split the work?  Because you can't have people working on the same table or query or report at the same time.  It just seems like a nightmare to me.  I develop extensive Access databases and much prefer to work alone.  I have an assistant, but I keep him mainly on troubleshooting and maintaining databases after I have created them.  Who knows how many problems you will run into.  Is this a school project or work?
324282
Access is great for "light duty" database work. If you've just got a few users, and you're not dealing with hundreds of thousands (millions is *really* pushing it) records, Access is fine.\n\nProblem is, Access is a file-based database, and, as a user, you pretty much have to open and wade through the entire file to find the records you need.\n\nOracle is a server-based database, so when you interact with it, you send a request to the server, which probably still wades through one or more huge files, but it does it very efficiently :-), and only sends the data you care about back to you.\n\nIt's better suited for large numbers of users, heavy usage and large numbers of records.
315742
Actually, there is a way, sort of.\n\nIn the Office Resource kit, there is a tool that will allow you to share an Access database (mdb) with other users, basically making your access db into an executable.\n\nCourse, you need the office Developer edition (or was it really in a resource kit?).  I'd suggest you do a search on microsoft.com's knowledge base.
1032537
Learn to use Microsoft Access and build it yourself.  You're not likely to get someone to write you a database for free.\n\nAccess has pre-built databases and wizards that spoon feed you through development.  Try it, you may enjoy it.
566403
Microsoft Access software can do that.
292988
Depends on the file that needs to be imported, and how you need to import it.  Enterprise manger comes with an import wizard that you can use to import information.  sometimes it's easier to just import the whole thing and delete what you don't need/want.\n\nanother way would be to make the file into a CVS and import that into access, then by using a linked table, export the table to SQL.
126598
sharing resources among many less powerful pc to create a  powerful database infrastructure
1739
There are a variety of ways to connect to an Access database from within a C++ app.\n\nThe oldest and most widely compatible is ODBC. It's not as fully featured as some other technologies, but it's the standard minimum compliance of pretty much everything.\n\nIf you're running on Windows, I'd suggest using ADO or ADO.NET. They're virtually the same interface, ADO.NET has some features that ADO doesn't have, but I'm not sure it's completely compatible with C++.
125494
Lot's of people do it.  Personally, if other considerations were roughly equal, I'd go with a non-proprietary SQL database rather than MS Access to keep open source as an option to being locked into MS.
747266
If you have a flow chart (as you should have), you could break the whole project down and have a larger number of team members work on subroutines or modules independently. You just have to have an agreed convention of GUI,  passing variables, and error trapping.
149111
Microsoft has a LOT of information online that will help you.  See the link below for a good place to start.\n\nThe help files also have code examples.  Just remember that Access and VBA (Visual Basic for Applications) have separate help files -- you have to be in VBA (e.g., via View -> Code) to see the help files for VBA.\n\nFinally, you can always ask questions right here!
130017
An Access database is just an ordinary file.  Use the My .ComputerFileSystem .CopyFile function.  This requires VB 2005.\n\n(Spaces added to foil Yahoo! mangling.)
785252
--being meticulous..\n--not being stubborn (you always have to be willing to learn)..\n--naming conventions for variables, filenames, tables, etc...\n--picking a specific language set to master instead of jack of all   trades...\n--knowing databases schemas\n--understanding how your program interacts with the database through networking.\n--OSI model\n--always thinking about automating in some fashion\n--the better you are at interacting with the user of your program for beginning specs, the better it will be for that person when it is complete (we are smart, but cannot read minds).
114358
bigbubba is right. SQL is far more stable when multi-user access is needed.\n\nif you cannot afford a SQL server, you can use MSDE from Microsoft which is free.
560387
Hello\nThere is some software that you can use , but I recommend ORACLE software they have a great database software with a great tutorial. \ngood luck there wonderful.
297617
I'm not sure what youm mean by electronic database, but why not use Microsoft Access?
171968
Microsoft Access has two built-in security features for protecting your database: \n• User/Group accounts and permissions \n• Database passwords \n\n---------------------------------------------\nBy using code, you can prompt for a password when a user opens a form or a report. If the correct password is entered, the form or the report is opened.\n\nThe following example shows you how you can password protect the Orders form in the sample database Northwind.mdb: \n1. Start Access and then open the sample database Northwind.mdb. \n\n2. Press ALT+F11 to start the Microsoft Visual Basic editor. \n\n3. On the Insert menu, click Module. \n\n4. In the module sheet, type the following procedure:\n\nPublic MyPassword\nPublic Function KeyCode(Password As String) As Long\n   ' This function will produce a unique key for the\n   ' string that is passed in as the Password.\n   Dim I As Integer\n   Dim Hold As Long\n\n   For I = 1 To Len(Password)\n      Select Case (Asc(Left(Password, 1)) * I) Mod 4\n      Case Is = 0\n         Hold = Hold + (Asc(Mid(Password, I, 1)) * I)\n      Case Is = 1\n         Hold = Hold - (Asc(Mid(Password, I, 1)) * I)\n      Case Is = 2\n         Hold = Hold + (Asc(Mid(Password, I, 1)) * _\n            (I - Asc(Mid(Password, I, 1))))\n      Case Is = 3\n         Hold = Hold - (Asc(Mid(Password, I, 1)) * _\n            (I + Len(Password)))\n   End Select\n   Next I\n   KeyCode = Hold\nEnd Function\n\n \n5. Press ALT+F11 to return to Access. \n\n6. In the Database window, under Objects, click Tables, and then click New. \n\n7. In the New Table dialog box, double-click Design View. \n\n8. Create a new table as follows:   \n   \n   Table: tblPassword\n   ---------------------------\n   Field Name: ObjectName\n      Data Type: Text\n      Field Size: 50\n   Field Name: KeyCode\n      Data Type: Text\n      Field Size: 25\n      Input Mask: Password\n\n   Table Properties: tblPassword\n   -----------------------------\n      PrimaryKey: ObjectName\n\n \n9. Open the tblPassword table and then enter the following data:     \n       ObjectName: Orders\n       KeyCode: 2818\n\n10. Create a new form in design view and save the form as frmPassword. \n\n11. Add a single textbox to frmPassword called Text0, and a command button called CheckPassword. \n\n12. Set the Input Mask property of Text0 to "PASSWORD" (minus the quotation marks). \n\n13. Add the following code to the OnClick Event of the CheckPassword button and then save the form:\n\nIf IsNull(Forms!frmPassword!Text0.Value) Then\n   MsgBox "You cannot enter a blank Password. Try again."\n   Me!Text0.SetFocus\nElse\n   MyPassword = Me!Text0.Value\n   DoCmd.Close acForm, "frmPassword"\nEnd If\n\n14. Open the Orders form in Design view. \n\n15. If the property sheet is not visible, click Properties on the View menu. \n\n16. Type the following event procedure in the module for the OnOpen property of the form:\n\nPrivate Sub Form_Open(Cancel as Integer)\n   Dim Hold As Variant\n   Dim tmpKey As Long\n   Dim I As Integer\n   Dim rs As DAO.Recordset\n   Dim db As DAO.Database\n\n   On Error GoTo Error_Handler\n   ' Prompt the user for the Password.\n   DoCmd.OpenForm "frmPassword", acNormal, , , , acDialog\n            Hold = MyPassword\n' Open the table that contains the password.\n   Set db = CurrentDb\n   Set rs = db.OpenRecordset("tblPassword", dbOpenTable)\n   rs.Index = "PrimaryKey"\n   rs.Seek "=", Me.Name\n   If rs.NoMatch Then\n      MsgBox "Sorry cannot find password information. Try Again"\n      Cancel = -1\n   Else\n      ' Test to see if the key generated matches the key in\n      ' the table; if there is not a match, stop the form\n      ' from opening.\n      If Not (rs![keycode] = KeyCode(Cstr(Hold))) Then\n         MsgBox "Sorry you entered the wrong password." & _\n            "Try again.", vbOKOnly, "Incorrect Password&qu