Page 3 of 3 FirstFirst 123
Results 21 to 22 of 22

Thread: Visual Basic and Access

  1. #21

    reply johnjack

    if you are useng vb as fornt end and acess 97 as back end u should try to handle constraints such as prinery key, enrorse data intigrity at the front end because giving constraints at the back end cuts the flexibility of using vb . u should try to enforce data entigrity at the vb ebd as much as possible

    u can open a recordset (rs.Open ("Ration_card_mast"), con, 1, 2)
    all the data in the table is retreaved in the recordset i.e. "rs" then u can one by one trasnsfer it into a array

  2. #22
    Senior Member Maestr0's Avatar
    Join Date
    May 2003
    Posts
    604
    Sice everyone has attached examples I will attach mine. This is just a sample app that uses VB as a front end to an Access 2000 DB for a little pretend store type thing with little shopping cart, however I dont like the ADO control **** so mine uses ODBC connector and passes actual SQL queries to the DB (So you can use any ODBC RDBM you want if you have the datasource). User must log in, Accounts are stored in the DB along with log entries like succesful logins or attempts etc. Keeps track of users totals and stuff,also has some OLE stuff. Hope this helps somebody, keep in mind its just a demo so the code doesnt do a whole lot of data validating against SQL injection or anything.

    -Maestr0
    \"If computers are to become smart enough to design their own successors, initiating a process that will lead to God-like omniscience after a number of ever swifter passages from one generation of computers to the next, someone is going to have to write the software that gets the process going, and humans have given absolutely no evidence of being able to write such software.\" -Jaron Lanier

Posting Permissions

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