Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Identity column, and DTC Formanager - positioning recordset

Status
Not open for further replies.

computergeek

Programmer
May 23, 2001
193
CA
Hello,

I have looked at other posts regarding the identity column. Thanks for your help.

I am now able to get the newly added identiy value back ... does anyone know how to "find the index value" of this newly added record in your recordset so I can do a move(index) to that record. I cannot seem to find a "find method" for the DTC scripting platform.

Note: Microsoft has a bug (Q190591) which ultimately places the user at the beginning of the recordset instead of at the newly added record. This is annoying!!

Thanks in advance for the advise.

 
You may find it quite easy to add the required (seek) function to the Recordset DTC code - in _ScriptLibrary/RECORDSET.ASP

This allows you to access the underlying ADO recordset, and use the seek method.

At the top of the _prototype function type:

_Recordset.prototype.seek = _RS_seek;

then find the _RS_move function, copy it and adjust for the seek logic and parameters.


Back in your ASP page, you should now be able to call the seek method
rsRecordset.seek "IndexCol", 123

unfortunately, VI will not include the seek method in its handy pop-up lists - but it IS there, if you added it!


(Content Management)
 
Hello,

Thanks MerlinB. I find modifying Recordset.asp kind of scary... Are we supposed to be modifying these "library" files? Have you done this before? I will be looking into this further today. Thanks for your help!

Computergeek
 
There is no problem with editing these files - so long as you keep to the same general layout. You will soon find yourself plugging the holes and adding in missing features. An immediate fix is to edit PM.ASP to recognise IE6 browsers as DHTML capable (function _SOM_isDHTMLBrowse)
!

Every new project gets its own copy of these files, so:
1. you have to copy your enhanced versions to all other webs, and:
2. if you get it wrong, there are loads of original copies here there and everywhere.

The master set are somewhere on your pc, so changing these will mean that all new projects will get the enhanced script library copied into it. (Content Management)
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top