As far as dropping a module and it creating a unique id.
Here is the code I am using in the various necessary file:

SQLDATAPROVIDER
[ModuleId] [int] NOT NULL,

VB FILE
Protected Sub InsertingItem(ByVal sender As Object, ByVal e As System.Web.UI.WebControls.FormViewInsertEventArgs) Handles FormView1.ItemInserting
e.Values.Item("UserID") = Entities.Users.UserController.GetCurrentUserInfo.UserID
e.Values.Item("ModuleId") = ModuleId.ToString()
e.Values.Item("ID") = 0
End Sub

INFO FILE
Public Property ModuleId() As Integer
Get
Return _ModuleId
End Get
Set(ByVal value As Integer)
_ModuleId = value
End Set
End Property



All values are being stored as "1", so I guess NOT NULL is working.
What am I missing to make sure Module ID's are being stored unique?


Feedback Appreciated,

-machina12

I am familiar with primary keys, but where am I to dictate that the ModuleID will be an identity key?

Can change within SQL DATABASE > MODIFY TABLE, but that won't update stored procedures.

I included code above for each section, are you saying it looks good?  Or what is it missing to make it an identity key?


-machin12

The problem is that the ModuleID & UserID are not being properly stored.

The primary key, running the ID column stacks numerically 1,2,3,4,5....
The module, no matter how many times it is dropped, is going is as ModuleID=1.
The UserID, no matter who is logged in, is going in as UserID=1

Using code from AdefWebServer tutorial, as posted above, should be storing values.
What am I missing to make each module it's own, as well as store info according to user?


Feedback Appreciated,

-machina12