Recent content by pelegs

"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...

Well, instead of: [type table]!typename & Format([qa table]![auto numb],"000000") I'd try: [type table]!typename & cstr([qa table![auto numb]) because cstr will always convert the number to a string, no matter how many digits. But still, your version is not causing the problem...

That's a good question. People who don't understand the Relational Model think they make grand Primary Keys(PK). In fact, using them as PKs breaks the model and you loose most of the advantages of having a Relational Database in the first place. OK, so Access isn't 100% relational, I know, but...

This is not so hard. When you first create the new row, assuming you can read the UserID, just make sure you insert that value in a column in the table. Now, if you want to keep an audit trail of who made a change, then you are in a more complicated situation. Do you want to keep track of just...

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...

Don't use a table at all. Make this information a property of the mdb. Peleg PelegNOSPAM@PStrauss.net

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...

You could look into this package: http://www.fmsinc.com/. FMS is one of the premier Access tool builders. Peleg PelegNOSPAM@PStrauss.net

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...