Ok Hi everyone,

I have searched the forums for something like what Im trying to do.  However have not been able to find anything. 

What I am trying to do is upload many users from a csv file.  I have a seperate user table from the DNN table.  But I need to populate both tables from an upload program I have written.  This is just the way the system I am building needs to run.

My users table control permissions to edit/view pages I have created.  And the Dnn user table controls DNN.  But I need the same users in both tables And I don't want to have to do separate uploads.

I am looking at building my own module to handle both uploads.  Is this tthe best course of action.  Or can I keep the upload separate (in one of my pages)  from DNN which is run from within DNN?

Thanks guys any help is greatly appreciated.

Joe.

I wouldn't...

One of the biggest problems of ALL dnn intensive routines (file sync., search indexing, portal templates) is that mostly they for batch inserts they use existing api, which often ends up by doing hundreds or more db calls and with any more serious project your things start to timeout and brake (not that dnn api is bad... but often it's not made for batch actions).

I would advise you to make a specialized batch insert routine (especially if you can use ado.net 2.0 which is more optimized for that and can do it async) and then mimic the dnn create user logic.

Hmm... the problem is not in using the API, the problem is using the wrong API for completly incorrect purpose - simply because you don't have an appropriate one. And forcing the usage of the same one just because it's there.

If you are loading a 1000 users into the database, from a web application... would you use a method which everytime for each user goes to the database, and adds them one by one? Yes you would (at least you do in source, many times over)... because you have create user API. Instead of thinking... ok this is a bigger batch.... maybe I need to develop a batch insert functionality which inserts for example 100 by 100 users, which can be performant and scalable in the long run?

One good example of this are Portal Templates.... lately I've been digging into the source because of some performance problems... and one example which I was horrified to find is when you are exporting a list of tabs to a template... for each tab the export procedure goes to the database to fetch it's modules, using the API. Now, if you have a small site... ~50 tabs you won't see the problem... but if you have a bigger site ~1000 pages... you will probably feel the pain... let alone other parts of the template. And that's because your using the API. And you could have written a query which in one pass gets all that info and only goes once to the database... but of course you would not use the API. And usually portal templates and such tools prove their worthness with bigger transfers and bigger loads, when it doesn't pay of to do it manually but instead have a tool which can automate the daunting task.

To conclude... I don't have anything against using dnn API, but to push it to users and to say and use it for every purpose, just to prevent the changes from occuring is just plain wrong in my opinion.