Search results

I concede the point that perhaps the poster was using a control not suited for the job. I will not, however, concede my point that snotty, holier-than-thou, and condescending attitudes prevail here. Anyone can deny it all they wish, but it won't change the fact. I think some of you need to take...

No Bob, I don't think it rude at all to help steer someone away from bad territory. The trouble is, far too many here assume every question is posted by someone who is already in bad territory. This attitude turns people off. I didn't see anything in the least troubling in the method being used...

Howsabout a little direct help to your actual question? Novel idea, I know... Me.txtWhatever = Me.cboWhatever.Column(x) Where x = the column of the combobox which contains model. Remember that ComboBox column index begins with zero.

I might ask why so many people here have the extremely annoying and rude habit of, instead of giving a halfway helpful answer, question every method used by the person asking the question. We should not care so much about the method the poster is using unless the poster is asking for help with...

Yes Keith, I know what it does. However, in my limited 15 year run, the only time I've seen an autonumber change is when I empty a table, run a compact and/or repair, close the db and run it again. Accordingly, I've often wondered why set Update on an autonumber field when it's never going to...

Is this scenario considered bad design form? (see attached image) I'll never delete a Customer or Site for whom a a Job exists. I need historical data to remain intact. I'll just mark a Customer or Site as [InActive] so they can't be used, when appropriate. If the relationships are considered...

I'm writing the .ResponseText from a WinHttp request into an .html file, then importing it with TransferText into a table, with a named Import Spec. I need to add a required field to the table which is not included in the tables from the .htm file. The value to fill it with is in the .htm file...

Sunday for me, as well, brainwise. I mean to say that the frontend won't work with an SQL backend without modifying it, unless you use linked tables. If banana mentioned somewhere that he (?) intended to do so, I missed it. Since the upsizing wizard will create the links for you, and banana...

I am speaking of a split database, Access front and back ends. In any context, "sizing" is not an appropriate concept, as the size of the db doesn't really have anything to do with it, unless your reason for "upsizing" is because you're bumping up against db file size limitations. I suppose the...

Your frontend won't work with an SQL backend without modifying it. So, no, upsizing is not just for backends. On the contrary, much more consideration must be given to the frontend when upsizing than to the backend. If your backend is properly indexed and named, it's a quick and painless upsize...

I won't address your questions specifically because I have not upsized a backend to SQL and rewritten the frontend to work with the backend. Also, I don't fully understand a couple of them. For example, I don't know how you intend to get data from the server, then manipulate it with DAO...

gemma, Not sure how applicable the form BeforeInsert would be here...I want to validate the text in the field first, to ensure the user isn't adding a duplicate customer. I have managed to do what I intended in the AfterUpdate Event. This works with the form bound or unbound. The only...

To pbaldy: Nope, no validation rule anywhere, other than the field being Required (in the db). The quick and dirty sample I posted has none either, but it pops up the validation error. I dunno Bob...doesn't seem to me that validating a required field on a form should be a big deal or even rise...

Ok, I think it was actually staying on the record then. Huh. Goofy thing. Thanks for looking. I'll get this worked out, one way or another. And I really thought going bound was going to be quicker :D

Thank you Bob, I will work in that event then.

Banana, did you not receive the validation error? I receive it, and am then able to move to the next new record, thereby saving the record with "test" in it.

Yes, the field must be Required.

While creating the example, I spotted the likely reason I get the error. The field is indexed, no duplicates. I still don't understand why a Cancel doesn't stop it. And the corresponding field in my project must be indexed.

2003 (11.6566..8132) SP2 This is only on a new record, mind you. I did further notice that after receiving the error one time, it all acts normally. Form remains dirty, so it's not because of that... I'll post my little example in a few mins. Thanks for taking a look Bob.

Well I tried a brand new control, both in my project and in a new database. There is no difference. On an existing record, it works as intended. On a new record, no dice. Me.Undo works for both an edited record and a new record. I don't want to wipe out the whole form for validation of one...