Hi, thanks for your replies. I am retaking now this issue.

My problem is the following.

As I said, I have two DB's:
* The DNN database (A).
* Another database (B), which holds presence control data, maintained by our Windows Forms software. This program collects the workers punches by polling the terminals and stores them in the DB.

I'm sure this is a very usual scenario, so my question must be something most beginners have faced.

I intend to create an employee portal in DNN which, among other things, would allow workers to list their punches and to manually create new ones.

I have been reading a few articles on the Web, as well as a pretty good book about custom modules in DNN; following its instructions, I created a Punches table in the DNN database, which contains the needed fields for the punches data: date and time, card number, etc., plus an ID, a ModuleID and an UserID field, which are used, as I undestand, by DNN. So, there is now a table called "punches" in db A which the same fields as another table also called "punches" in db B, plus ID, ModuleID and UserID.

I have successfully created a custom module that allows users to, for example, list or create their own punches. But the problem is the data they see is in the DNN database (A), not in B, where all the employees and presnce control data resides.

If I want my module to point to database B, do I need to modify the table and create the additional fields ID, ModuleID and UserID in the punches table in db B?

Or should I use a linked server to access the real employees data in db B from db A?

Thanks a lot,

Dani

Hi, I'm sorry I guess Cathal already answered my question whe he said that provider architecture is assuming it connects to the DotNetNuke database, not any other one,

Thank you very much.


Daniel Carbonell