| Author |
Messages |
|
keithcstone
Posts:2
 |
| 04/03/2007 6:51 AM |
|
Some things I’d like to see:
* Support for timestamp fields. Ignore them on forms, don’t try to update them in stored procedures, but compare them to see if someone has update the row out from under you in the stored procedure. Easy to do, I can send examples of SPs if you wish.
* Support for date-created / modified. The ability to flag a field as a place to put the last update date and date created. This would be displayed, but updated only in the stored procedures. This is a common need.
* Support for user-updated/created. Flag a field to be populated with the userid when the row is updated or inserted.
* Master / detail. If I have a contact with multiple phone numbers or emails, etc.
* Lookup tables. Allow list boxes to be populated from a table instead of a hard-coded list.
(as a hint, you may want to look at http://www.hkvstore.com/aspnetmaker/ for ideas. :)
As example stored procedure is:
CREATE PROCEDURE dbo.ContactsUpdate
@PortalId int,
@ContactType int,
@FirstName nvarchar(16),
@MiddleName nvarchar(16),
@LastName nvarchar(32),
@Suffix nvarchar(6),
@Nickname nvarchar(24),
@BirthDate smalldatetime,
@ModifiedBy nchar(100),
@Version timestamp,
@ContactId int
AS
UPDATE dnn_ClubContacts SET
PortalId = @PortalId,
ContactType = @ContactType,
FirstName = @FirstName,
MiddleName = @MiddleName,
LastName = @LastName,
Suffix = @Suffix,
Nickname = @Nickname,
BirthDate = @BirthDate,
DateModified = GetDate(),
ModifiedBy = @ModifiedBy
WHERE
ContactId = @ContactId AND Version = @Version |
|
|
|
|
host
Posts:93
|
| 04/03/2007 7:51 AM |
|
* Support for timestamp fields.
This should be in 4.5
* Support for user-updated/created.
Currently, the UserID field does this by default. Whenever a record is added/updated the UserID reflects the logged in UserID.
* Master / detail. If I have a contact with multiple phone numbers or emails, etc.
This is accomplished across modules in MB. Take a look at step 5 of the Demo. All of those modules are master/detail.
* Lookup tables. Allow list boxes to be populated from a table instead of a hard-coded list.
Use the Option Value BUilder to populate list boxes statically, from another module or via a Sql statement.
Brian Sammons |
|
|
|
|
|