Wrox Programmer Forums
Classic ASP Databases Discuss using ASP 3 to work with data in databases, including ASP Database Setup issues from the old P2P forum on this specific subtopic. See also the book forum Beginning ASP.NET Databases for questions specific to that book. NOT for ASP.NET 1.0, 1.1, or 2.0.
Welcome to the p2p.wrox.com Forums.

You are currently viewing the Classic ASP Databases section of the Wrox Programmer to Programmer discussions. This is a community of software programmers and website developers including Wrox book authors and readers. New member registration was closed in 2019. New posts were shut off and the site was archived into this static format as of October 1, 2020. If you require technical support for a Wrox book please contact http://hub.wiley.com
Old December 19th, 2004, 12:32 PM
Authorized User
Join Date: Aug 2003
Posts: 54
Thanks: 0
Thanked 0 Times in 0 Posts
Default Multiple Recordsets from Multiple Tables

I'm going to attempt to create multiple recordsets from multiple tables that are located within a single Access database. The tables are not relational.

Any suggestions or words of warning regarding a best method or approach for saving resources and avoiding problems?

Best regards,
Old December 19th, 2004, 10:45 PM
Friend of Wrox
Join Date: Sep 2003
Posts: 363
Thanks: 0
Thanked 1 Time in 1 Post


  what is your actual need. How come a database without relations for many tables(as u specified)? You can have many recordsets but it put burden on server.

If your database tables dont have any relations means we have to suspect database design????

make it clear.


Old December 28th, 2004, 12:45 PM
Authorized User
Join Date: Aug 2003
Posts: 54
Thanks: 0
Thanked 0 Times in 0 Posts

Sorry for the extended delay in responding. I made two attempts to post while on the road, but problems with the host's server kept it from being posted.

Anyway, I have to agree on the database design issue. In this case, a relational database could be created, but would be overly complicated for what is actually required.

In short, I have a main table that stores a customer ID, a product ID and two registration numbers.

For each product ID, there is a separate Password table that includes two fields, a registration number and the associated password.

At the end of the transaction, one or more of the passwords from the appropriate Password table are given to the user, based on the registration number(s) provided in the main table.

In most applications, I would create a link or relationship between the Registration number fields in the main table and the Password table. However, because the Password table to link to is dictated by the Product ID, the Registration fields would have to be tied to multiple Password tables. I believe this is a Many-To-Many relationship.

To create such a relationship doesn't seem very organized, and to create a clean relational system, while still possible and feasible, would mean creating a whole bunch of other tables that unnecessarily expand the size of the overall database without really adding any benefits.

Then again, as I'm fairly new at all this, I could be all wet.

Again, thanks, and have a great Holiday season.

Best regards,

Similar Threads
Thread Thread Starter Forum Replies Last Post
multiple recordsets returned BCullenward Classic ASP Basics 7 July 28th, 2006 04:16 PM
closing and cleaning up multiple recordsets Loralee Access 1 September 26th, 2005 05:46 PM
Importing Multiple files in Multiple tables Versi Suomi Access 6 June 1st, 2005 08:47 AM
Multiple tables with relationships Please Help Lesviper Access VBA 6 February 3rd, 2005 08:20 PM
dataset with multiple tables Bhavin Crystal Reports 2 October 8th, 2004 09:18 AM

Powered by vBulletin®
Copyright ©2000 - 2020, Jelsoft Enterprises Ltd.
Copyright (c) 2020 John Wiley & Sons, Inc.