Validation and More. And More and More.

by Peter Tyrrell Tuesday, October 04, 2005 5:19 PM

We bought Peter Blum's validators and more package just recently. Everyone says it's better than sex for ASP.NET edit pages. Then again, that's the kind of thing your average .NET developer WOULD say. Unremediated social misfits, the lot. But I got more than I bargained for when I started working with them today. The validation controls, not the misfit developers. First clue was opening the user's guide, and seeing it was 235 pages. And, oh wait, that was only one of the user guides. There were a couple more, plus a tutorials PDF. I think it all added up to about 500 pages. Of instructions. Gawd. I slumped into instant depression. It's an in-depth package. It's going to do everything, and I'm going to be able to retire early with Peter Blum's Validation and More running the whole show for me. And now it's the end of the day, and I can say I have implemented exactly one (1) validation control that makes Title a mandatory field. I don't know whether to shoot myself or have a party.


Fetch record after ODBC INSERT the Guid way

by Peter Tyrrell Monday, October 03, 2005 9:15 PM

I remembered today, with Ted's help, a technique which I really dig for retrieving the just-created textbase record when using ODBC Insert. 'Cause you don't get back any textbase-produced stuff like an autonumber RecordID or DateTimeEntered or anything, when using Inmagic ODBC to insert a record. There's just this kinda whistly sound the little integer-that-could makes as it tumbles its tumbleweedy way back from the database. "1" for "ayuh, I reckon we got ourselves a new record", and "not 1" for "they saw us comin' and Li'l Joe's been shot!" Or. Yeah. And that is the lamest wordplay ever in a title.

Okay so, I have used things like SELECT MAX(ID) FROM [tb] WHERE Title = ? to fetch what I just inserted, not yet knowing the ID, since it's produced in the BLACK BOX down there where the database is. And that's worked because it's unlikely that a field like Title, even when not unique, is going to repeat often, and since each new ID is an integer based on last-produced-integer +1, it's very very likely I'm going to get the record back that I just inserted.

Ted and Nathan have used unique fields or field combinations that have a statistically high unlikelihood of repeating. But still, it's bothered me that the method is not airtight. And today I remembered something Nathan had come up with: produce a GUID, stick it into the textbase along with the rest of the record, fetch record by GUID. So simple and effective. One needs to add a new field for it, but so what? And creating a string GUID in VB.NET is dead-easy: System.Guid.NewGuid.ToString().

Ahhh. Relax... the Andornot Way.

Tags: Inmagic ODBC

IIS reset methods

by Administrator Sunday, October 02, 2005 9:41 PM
When Inmagic instructions say "Reset IIS" remember that this means to restart the World Wide Web Publishing service, not to just use the command line or stop and restart IIS from the IIS console. This ensures that any changes to the dll or .cmx file are loaded. See:


Blog splits in two

by Peter Tyrrell Sunday, October 02, 2005 7:04 PM

Due only to my own sense of decorum [ggggmmmffff-harf harf harf] I have elected to continue personal blogging on my personal site at, and stick to andornot-related topics here. No one made me do this, it just seems right.


Month List