Search results

Can't... Where do you think you would place that logic? It will, at best only evaluate the first row of output and then make all rows the same (either T or F). The only way I have found to get around these issues in Access, is to handle it in the SQL of a query, and then base your tabular...

Not so fast my friend... In VB, you can get the number of elements in the control array. You then can iterate through each row (albeit that row 8 might be first and row 1 might be last now) and perform your operation on the row, because all of the other information for the record will still be...

The answer is: The reason a user would have to go through and click on every record, is that the onCurrent event (a.k.a. Form_Current) for a tabular form is kicked off when you open the form and when you click on the record selector. When you open the form, the Form_Current doesn't fire off...

Wow, I didn't know that Pat and Rich work for MS (Just kidding guys)...let me see if I can address these: I suppose you're right...If you want to go through and click every single record in the form!!!!!!!! Pat, I think you're missing the mark just a little bit. The identifier correlates to...

That's all well and fine, but... If I can do it on the web, I should be able to do it in Access! If you create a control on a tabular form, it wouldn't take much effort for Access to create a control array, and you would reference the control by its name + the identifier. Most programmers...

Here is a handy-dandy quote: -- This quote was taken from the Access Help File when doing a lookup on "Exclusive"...hope it helps.

Emphatic NO! Sorry, but as I have come to learn, the intuitive "As You Go" event -- referred to in Crystal as "While Printing Records" -- is not exposed on a tabular form. This seems intuitive to me, but apparently not to Microsoft. Anyone who understands this differently, feel free to speak up.

Oh... I'm sorry, I didn't know it was one of those "Love/Hate" relationships

A little harsh, don't you think? Everyone has to start somewhere, I hope you don't tell kids they're stupid when they ask you questions.

Here ya go... Private Sub MyButton_Click() DoCmd.RunSQL("ALTER TABLE myTable ADD COLUMN myNewColumn TEXT(30)") End Sub For more information, visit this link Cheers!

Here ya go... strName = mid(strName, instr(strName, ",") + 1) & " " & left(strName, instr(strName, ",") - 1) Cheers!

You're going to love this... Since you are using a tabular form, there is no way to reference an individual cell within the tabular form (i.e. ModuleStatus in your case). If I say ModuleStatus = "Alabama" how does it know which one to change? So, it only changes the selected one. This is by...

EXEC I don't know about the whole EXEC thing that I was talking about (works fine in SQL Server, but I can't find any definitive information about it in Access). Sorry I can't be more help.

...stop the press I'm looking into that last solution I gave you "EXEC..." it looks like I might have been smoking too much crack before I posted that. I'll let you know here in a moment.

or...else... Well, that clarifies things for me a little bit. I think your best resolution will probably be to do it all in separate queries (and not try to put your 30 into 1). The reason I say this, is that the effort won't save you much if any coding (You will still have separate criteria...

Access XP If you want, I can check on that for you when I get home tonight. I have Access XP at home, but not at work. I can check and see if it has the functionality you desire and let you know.

Seems to work for me... I am using Access 2k and it seemed to work for me.

Only if you try and do it all within Access VBA associated with an Access form was not designed to do what you want to do. As such, MS provides a workaround to do it all within Access, but at a (potential) cost. It does not say that after you quit and restart that if you go into the VBE that...

I'm still at a loss... I don't fully understand your need to write that many queries. Can you elaborate any more on the specifics of your issue?

Well... ...you are going to touch the same number of records no matter what (so, the user is going to get prompted each time); however, there is a work around. I would assume that you are doing something like this: DoCmd.RunSQL (Your SQL Statement Here) All you need to do is add...