Can somebody please explain Microsoft Access?
414169
Access is Microsofts attempt to do databases which is horrible. SQL or Oracle are better but people still use that for some reason. Below are links on Amazon for books on Access 2003 best is to just follow through one of those and fumble around to teach yourself.
1015496
Access has the "forms" but I forget how to use it.
1197
Microsoft Access 2003 for Dummies is a real good book and can be found in many bookstore cross the America
862897
Go for MS-Excel or MS-Access.
860809
You can try going to http://www.download.com and see what you can find in there. They have everything from FREE-ware, shareware to stuff you have to pay for. It's DEFINITELY worth a look-see ;)\n\nAnd, yes, Access is designed to do exactly what you are wanting to do. If you don't have it then go get the M$ OFFICE Suite and some books on the program from your local bookstore to learn how to use it.\n\nOR you can try http://openoffice.org and see what they have there. I've only heard about it but it comes to me as highly recommended.
950967
Basically MS-Access is for small scale industries/businesses - thats what microsoft itself is claiming. MS Access cannot handle records more than say a few thousands. I myself have experienced it - after 80000 records - MS Access really struggles. However MS SQL Server is quite capable of handling large number of records/data - so does ORACLE.\n\nFor your requirement, MS Access will be just fine.
948329
It sounds like you are using a linked table that does not have a primary key. Without a primary key, I think Access looses track of which row is which, and gets this error. Even if you don't want to use a primary key, you could add a primary key column to the backend table (for example, with an auto-increment value) just for Access to use. Then you can leave that column out of your queries in Access.
283150
Here's a code snippet that you should be able to paste into a form module and give it a try ... there are obviously many ways to tackle the issue ... this is just one of them.  To use this code you'll need a reference in your VB6 project to a Microsoft ActiveX Data Access Library (like 2.6).  Good luck!\n\nDim rs As Recordset\nDim cn As Connection\n\nDim DBPath As String\nDBPath = App.Path & "&#92;customer.mdb"\nSet cn = New Connection\ncn.Open "Provider=Microsoft.Jet.OLEDB.4.0;Data Source=" & DBPath\n\nSet rs = New Recordset\nrs.CursorLocation = adUseClient\nrs.Open "SELECT * FROM tblCustomers WHERE CustomerID=" & 1, _\n    cn, adOpenStatic, adLockOptimistic
942246
Try this online tutorial - it is brilliant. Not only does it have downloadable pdf files covering various topics on Access, but also exercises and example databases.\n\nhttp://www.cob.ohio-state.edu/~muhanna_1/837/MSAccess/tutorials.html\n\nHope this helps.
1053391
Programme Files&#92;Microsoft Office&#92;Samples\n\nMeaning, in the microsoft office directory. could be as follows:\nC:&#92;Programme Files&#92;Microsoft Office&#92;Samples\n\nYou can browse to it from "My Computer"\n\nOr you can go to your Access Program, click on file open and then browse to it from there.
462677
You can use Tables from MS Access or MS SQL Server Already loaded with Data
153544
Microsoft offers a full family of database tools for the desktop, the server, and for open connectivity. For the desktop Microsoft offers Microsoft Access 97/2000.\nThe Microsoft Access 97/2000 is a full-featured multiuser relational database management system that designed for the Microsoft Windows operating systems (such as Windows 9x, Windows NT, Windows 2000). Access 97/2000 is extremely visually oriented and easy to use. It makes extensive use of drag-and-drop and visual design for queries, forms, and reports.\n\nAccess 97/2000 comes with an integrated development environment (IDE), including incremental compilation, a fully interactive visual debugger, breakpoints, and single step-through. These capabilities combine to make Microsoft Access an extremely powerful platform for developing client-server database solutions.\n\nThere are general Access 97/2000 characteristics:\n\nObject Maximum sizes/numbers \nDatabase size 1 Gb \nNumber of characters in an object name 64 \nNumber of characters in a password 14 \nNumber of characters in a user name or group name 20 \nNumber of concurrent users 255 \nNumber of characters in a table name 64 \nNumber of characters in a field name 64 \nNumber of fields in a table 255 \nNumber of characters in a Text field 255 \nNumber of characters in a Memo field 65,535 / 1 Gb \n\nThough the maximum database size is 1 Gb, but your database can include linked tables in other files, and its total size is limited only by available storage capacity.\n\nNumber of characters in a Memo field can be up to 65,535 characters when entering data through the user interface or can be up to 1 Gb when entering data programmatically.\n\nAccess 2000 can lock on the row level in comparison with Access 97 page level's lock.\n\nWHILE IN SQL SERVER 2000\n\nThere are no many differences in the internal architecture between SQL Server 7.0 and SQL Server 2000. SQL Server 2000 has the same features as SQL Server 7.0: autogrow features, new storage engine, complete row level locking and so on. So, the general characteristics of these versions are the same.\n\nThere are general SQL Server 97/2000 characteristics:\n\nObject Maximum sizes/numbers \nBatch size 65,536 * Network Packet Size \nBytes per short string column 8,000 \nBytes per text, ntext,or image column 2 GB-2 \nBytes per index 900 \nBytes per foreign key 900 \nBytes per primary key 900 \nBytes per row 8,060 \nBytes in source text of a stored procedure Lesser of batch size or 250 MB \nClustered indexes per table 1 \nColumns per index 16 \nColumns per foreign key 16 \nColumns per primary key 16 \nColumns per base table 1,024 \nColumns per SELECT statement 4,096 \nColumns per INSERT statement 1,024 \nConnections per client Maximum value of configured connections \nDatabase size 1,048,516 TB \nDatabases per instance of SQL Server 32,767 \nFilegroups per database 256 \nFiles per database 32,767 \nFile size (data) 32 TB \nIdentifier length (in characters) 128 \nLocks per connection Max. locks per server \nNested stored procedure levels 32 \nNested subqueries 32 \nNested trigger levels 32 \nNonclustered indexes per table 249 \nObjects in a database 2,147,483,6474 \nParameters per stored procedure 1,024 \nREFERENCES per table 253 \nRows per table Limited by available storage \nTables per database Limited by number of objects in a database \nTables per SELECT statement 256 \nTriggers per table Limited by number of objects in a database \nUNIQUE indexes or constraints per table 249 nonclustered and 1 clustered \n\nSQL Server 2000 Enterprise Edition on the Windows 2000 DataCenter can support up to 32 CPU and up to 64GB physical memory (RAM) on a computer!
470488
MS Access comes with some sample databases.  Other than that, you just have to look for some.
421773
MS access will do that, \n\nlookfor help in excel for JET or OBDC
744551
**********************************************\nIn short MS SQL is a language used to manipulate databases via codes SQL meaning Structured (or Simple) Query Language\n\nMs Access is a WYSIWYG (what you see is what you get) Program to create databases\n**********************************************\n\nNOT SO SIMPLE...\n\nThe fundamental difference is that MSSQL is client/server RDBMS and Access is file-based. MSSQL has a server side component (databse engine) that always need to be running before you can connect to any databses and you need to get a client component (GUI e.g. SQL Enterprise Manager, query analyser, etc) in order to connect to the server component. Access is actually a Jet engine database and you use MS Access as the GUI. MS Access offers you excellent GUI tools to manipulate the data in the .mdb Jet database file. However, you can connect to access from other GUIs e.g. VB6 IDE. You can research on file based vs server based databases.\n\nBoth are SQL databases, which is by the way a language itself. The SQL standard describes a common language for manipulating and defining data in compliant database management systems. Thats how you can write a VB6 app for example which uses an access backend, and not need to have MS Access installed in order to access the data in the .mdb file.\n\njust google something like mssql vs access and sift through the results.\n\nhttp://www.cypressinland.com/access_vs_sql.htm\n\nThis is a good comparison (MSDE is scaled down SQL Server):\nhttp://msdn2.microsoft.com/en-us/library/aa140017(office.10).aspx
1127319
we used microsoft ACCESS here at work; this program is very powerful and will help you organize, see and print information on customers or other records in a variety of forms, this is useful if you have data that you'll be inputting yourself electronically\n\nif you have a lot of paper that you want to store electronically the way to go would be to get a high-speed, high quality scanner (these can be leased) and either buy a big file server or burn the stuff to CDs
948763
access can import many types of files,  it looks for a hard carraige return to seperate each records out.  You can seperate the fields with comma's.  Then import them into access.  This might not be an easier solution, please let me know if you have any questions. \n\nHope this helps.