Access 2007-2019
Access 2000-2003
Access Seminars
TechHelp Support
Tips & Tricks
Access Forum
Course Index
Topic Glossary
Insider Circle
 
Home   Courses   Seminars   Templates   Help   TechHelp   Forums   Contact   Join   Order   Logon  
 
Home > Courses > Access > Developer > D24 > < D23 | D25 >
 
Access Developer 24

Reservation System, Copy Record with Children


 S  M  L  XL  FS  |  Slo  Reg  Fast  2x  Buy Now

Welcome

Developer 24 continues our study of Recordsets. We will build a reservation system that you can use to reserve an item, hotel room, etc. and it will handle conflict resolution (no two reservations on the same dates). Then we will learn the right way and the wrong way to copy a record along with it's dependent child records, for example an order and all of its detail items.

Resources

Topics Covered

In Lesson 1, we will go back to the Rental History database that we build in Developer 23 and add a future reservation system to it. We'll be able to reserve an item (or tool, room, car, whatever) for a particular customer between two dates. We'll set some arbitrary rules for our fictitious company, such as the reservation must be in the future, but no more than 1 year in the future. It must be a minimum 1 day, but maximum 2 week rental. Finally, we'll check for conflict resolution so that two reservations don't overlap. This is the hard part!

In Lesson 2, we learn the wrong way to copy and paste a record along with its dependent child records, for example an order and its detail items. I show you the wrong way to give you a better appreciation for the right way which is coming in Lesson 3, but there are still some good topics covered in this lesson, for example how to delete a record and automatically delete the child records without using Cascade Deletes, which you lose in linked tables (no Referential Integrity).

In Lesson 3, we learn the right way to do the same thing we did in Lesson 2. We'll create a couple of recordsets to copy the order info and the detail items. We'll learn how to loop through the Fields Collection of a recordset so we don't have to manually copy each field at a time. This will "future proof" our code. If we add fields to the tables in the future, we don't have to worry about updating our code!

Enroll Today

Enroll now so that you can watch these lessons, learn with us, post questions, and more.

Questions?

Please feel free to post your questions or comments below. Thanks.

 

Start a NEW Conversation
 
Only students may post right now. Click here for more information on how you can set up an account. If you are a student, please LOG ON first.
 
Subscribe
 

You may want to read these articles from the 599CD News:

5/9/2021Access D29 Started
5/9/2021Access Developer 30
5/9/2021Access Developer 30 Lessons
5/9/2021Access Developer 30
5/8/2021Data Entry
5/2/2021Split Commissions
4/30/2021Close Form
4/30/2021Close All Forms
4/29/2021Quick Queries #3
4/26/2021Combining Names
 

Learn
 
Access - index
Excel - index
Word - index
Windows - index
PowerPoint - index
Photoshop - index
Visual Basic - index
ASP - index
Seminars
More...
Customers
 
Account Login
Online Theater
Downloads
Lost Password
Memberships
Student Databases
Change Email
Info
 
Latest News
New Releases
User Forums
Topic Glossary
Tips & Tricks
Search The Site
Code Vault
Collapse Menus
Help
 
Customer Support
Web Site Tour
FAQs
TechHelp
Consulting Services
About
 
Background
Testimonials
Jobs
Affiliate Program
Richard Rost
Free Lessons
Mailing List
Order
 
Video Tutorials
Handbooks
Memberships
Learning Connection
Idiot's Guide to Excel
Volume Discounts
Payment Info
Shipping
Terms of Sale
Contact
 
Contact Info
Support Policy
Email Richard
Mailing Address
Phone Number
Fax Number
Course Survey
Blog RSS Feed    Twitter

YouTube Channel    LinkedIn
Keywords: access developer 24 duplicate records copy record with subform copy related  Page Tag: whatsnew  PermaLink