Yes, you should be ably to do this by setting up 2 doctypes and 2 data connectors for them. Keep in mind, though, that the Database Accelerator uses a "fire-and-forget" model. It roundtrips the XML forms as "blobs" which is great because it keeps complete XSD data type fidelity, but data shredded to the DB is just shredded. It does not rehydrate from the relational schema in the DB. Of course, subsequent edits shred to same rowset. This model is great for people who want to use SQL for reporting, archival and as a entry point to other line-of-business processes. It's also very good for mapping to an existing DB since it requires no changes to the relational schema.
The problem with rehydrating from SQL is synchronization of multiple writers. With Database Accelerator, the Web service does the locking, but if we were to support out-of-band other-app updates to DB we would have to significantly modify existing databases to support locking, permissions and round-tripping. With the fire-and-forget, we don't have to, but users can only modify forms using the Database Accelerator.
Hope this helps.
Patrick Halstead [InfoPath MVP]
InfoPathDev
Patrick Halstead
Project Manager at Qdabra