"About Uptdating the column with the current
UserID whenever a row is modified
how do i do that.?"
If you are using a bound form, this is not very difficult. Say the column is called "UserID" and that the current UserID is in a variable strUserID. (How it gets into that...
...here is that I wouldn't bet you a plug nickel that your data is reliable. And yes, since this app is "rather crucial to our business", I *would* be loosing sleep over it if I were you. You have an important app, written by amatuers. Look at it this way: would you hire a kid with a...
...I never show the column to the user on any form, and I never even mention to them that it is even there. It is indexed, of course, but is *not* the PK. I never make use of the value, I don't ever care what the actual value is, except that it is unique. I don't do any calculations on it, as...
...change to the row? Then that's not so bad. Just update the column with the current UserID whenever you modify a row.
If you want an audit trail of *everyone* who changed the row, then, you're at the next level of complexity. You need a separate audit trail table for each table you want to...
You should put the DoEvents in some processing loop somewhere and call it about every 100, or 200, or 500 times around. Experiment a little and see what works.
What you saw is this: when Access is running a compute-intensive piece of code, it hogs all the CPU cycles it can get. The Task Manager...
Only thing I would add is that instead of using DMax, write your own Select. All of the the Domain Aggregate functions are known to be terribly slow. The SQL to do it yourself is simple:
Select column From table Order By column Desc
and then just return the value of the column in the first row...
You should never depend on any particular value being in an autonum. Better to make your own numeric column, and take care of incrementing it yourself (gee, I wish Access had triggered procedures). Good advice about not storing the concatenated value. The way you are attempting to use the...
No one has really answered the question. You can force autonums to start wherever you want and number them sequentially from there (assuming you are not using the random option), as explained, but you can't insert a number below any one that is already there. You can't set the value of an...
Comment One:
In order to NOT have to count commas, you could also pass "By Name", as follows:
DoCmd.OpenForm FormName:=stDocName, OpenArgs:="some string"
The Intellisense reveals the exact name you need to use, and note that the delimiter is ":=", not just...
Jeremy,
You've encountered situations in which you can't get the phone, but not situations in which you can't get the address?
The situation was that a name was obtained as a referral. We actually had to handle the situation where we only had a name and not much else. My contention was that...
Could be you need to reverse the order to Chr(10) & Chr(13)? Sounds like they are both getting in there, but Access is not so forgiving about which comes first, and I haven't a clue which is it supposed to be, so it is worth a try. Alternately, try this function in place of the Chr functions...
JeremyNYC said:
Those PKs should be autonumbers. Having significant PKs only leads to headaches.
Well, then, why use a PK at all? That is not what a PK is supposed to be. They are supposed to be one or more columns from the naturally occuring data. Now, I know a lot of people don't agree with...
Use an intermediate table that maps references to citations. So, it would have rows that look like this:
Ref_R1_ID, Cit_C1_ID
Ref_R1_ID, Cit_C2_ID
Ref_R2_ID, Cit_C3_ID
Ref_R2_ID, Cit_C1_ID
and so on.
Now, when you delete the reference Ref_R1_ID, just delete all of the Ref_R1_ID rows. There is...
I'd redesign the table. I'd split the ID into to parts, Category and Number. That's what the ID really means. If you need to display something like "f003", just paste them back together. It is usually easier to paste columns back together on-the-fly when needed than to take them apart...
I'm not all that familar with ActiveX controls, but I seem to remember that not all are created equal. Some might not be compatible with Access, and yours might be one of them.
Where did the control come from? Is it touted as being Access-compatible?
If so, try this. Sometimes Access gets...
I'd like to clear up a matter. Most properties of a control on a form are not tied to the data being displayed. On a contiuous form, it is like getting a copy of the form, over and over. When you set the properties, note there is only syntax to support changing a property for the control, and...
Interesting problem. When it didn't work, what happened?
I can suggest that what you need to do is grab the RowSource of the listbox and push that into the RecordSource of the report in the report's OnOpen event. Something like:
Me.RecordSource = Form_FormName!ListBoxName.RowSource
You need...
GK:
It seems like you understand it pretty well. You mentioned something about some logging and errors tables. I suggested that these be put in another mdb simply because it would be easier to flush these tables periodically if they where in a separate mdb. This is also in line with the idea of...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.