Multiple tables best practices - InfoPath Dev
in

InfoPath Dev

Multiple tables best practices

Last post 03-23-2009 05:33 AM by Vedran. 0 replies.
Page 1 of 1 (1 items)
Sort Posts: Previous Next
  • 03-23-2009 05:33 AM

    Multiple tables best practices

    What are best practices regarding case when one has one fom that is representing front-end for database that has multiple tables which have defined relationshio between them?

    For example, there is a "central" ServerTable which has defined basic info about server. There are also n additional tables that store more info about particular server. CommentTable, DailyChangesTable ... These tables have primary-foreign key relationship defined between them.

    I have decided that, I will make use of webservice to connect InfoPath with SQL database using ADO datasets.

    What are the best practices for this kind of scenario? As I see, there are two options:

    1. Make one main receive/submit connection - the problem here is when there is a field in "additional" table that must be filled (doesn't allows null values). For example, when are you trying to create new server record, you must also fill required values in other tables (required date in DailyChangesTable). You should be able to create new server without any comments. Since I'm a new to IP, I do not see way to this with one main receive/submit.

    2. Make submit for each table and one receive connection (this receive connection will return entire database) - main disadvantage here is to know how to see that changes occured and apply appropriate SQL command (insert, delete, update) to the dataset.

    I hope that these dillema makes sense to MVPs. :)

     

    Filed under: , ,
Page 1 of 1 (1 items)
Copyright © 2003-2019 Qdabra Software. All rights reserved.
View our Terms of Use.