Search results

Re: Audit trail snag Mine are almost always set up with: "Enforce Referential Integrity" box checked "Cascade Update Related Fields" box checked Join Type #1 Also if the Record ID in tblDatabaseChanges is set to no duplicates, it likely isn't going to work the way you want it to. Make sure...

Re: Audit trail snag I have mine setup a tad different but the first thing that comes to mind from your description is: Do you have your main equipment table and tblDatabaseChanges relationship set correctly? By the sounds of it the relationship is set to one to one instead of one to many.

Not sure if it's something as simple as this but this came up in a search. http://www.access-programmers.co.uk/forums/showthread.php?t=107541

One issue I had with this is if I had the focus on a command button and that button was in the same detail area the input boxes were in, the function wouldn't work.

Thanks. I'll have a look at that too. I'm pretty bamboozled now as to why everything started working again. But since it does, now I can go back to my development. I'm still going to use your code because it makes sense to do it that way.

Thanks for the reply David. To answer your questions: Yes "rst" is declared - I have a separate module where I declare my most common items: e.g., "Public RST as DAO.Recordset". That is ok. DAO is referenced properly. Now I am really puzzled. I used your code, and now the error is being...

I have a weird problem I can't seem to get a grasp on. I have a split database in Access2K. I have the code below to check the link to the backend: Function Check_Links() As Boolean On Error GoTo Error_Handler 'Checks for the connection to the backend Check_Links = False...

You can modify the code to reflect the ID in your table. It doesn't necessarily have to be named RecordID. Just make sure the name in the code match the names in the table. What line is being highlighted on the compile error? Yes - Remove this part of the code: If frm.NewRecord = True...

My response was geared toward the lack of network logins. He can still create custom DB logins (not Access Security) and each employee logs into the db. Then you CAN figure out who did what. That was in response to your statement: No need to become defensive, and I still disagree with the...

Ok. In my example, "Function COTH(byVal X as Double) as Double" I have been able to add the description information to COTH. Can anyone point me in the right direction to add a description for X? Thank you.

Can anyone tell me how to add a custom description to my user-defined functions? As an example, see the attachment. I've outlined it in red. So if I write a custom function: Function COTH(byVal X as Double) as Double How would I describe what the function is when a user calls it? Thanks

I tend to disagree with this. Just because there are no network logins, does not mean you can't figure out which pc it came from and when. Creating your own log-ins, disabling the shift key, menus, etc is a step in the right direction. It won't be perfect, but he can surely make it extremely...

I'm not sure if you are using my code example or not, but my example works fine in MDE format (see attached).

I'm also in favor of not storing images in the database. Generally I use links and store in a separate folder in the root folder. However, I do have a few apps that it was requested to store images/files, tied to a record. One app stored images, and the other stored 1-3 page pdf documents. In...

You could also save the record this way before printing: DoCmd.RunCommand acCmdSaveRecord

Thank you for that explanation and analogy. It makes perfect sense. I've always seen it done both ways where the string is released (tmp = "") and others where it is not. I've only ever released when I use objects such as DBS and RST. I've only ever cleared a string when I found I caused an...

What if they are not declared "PUBLIC" but still declared outside the procedure? IE: Option Compare Database Option Explicit Dim sSQL as String Dim sPrompt as String Function Whatever()..... In my scenario, I have 3 procedures in a module, two of which use the above variables...

When constructing strings in vba (SQL statements, MsgBox prompts, etc) is it necessary to clear the string when exiting the function/sub? Meaning is it necessary to do something like this at the end of the code: sSQL = "" or sSQL = vbNullString sPrompt = "" or sSQL = vbNullString

I assume your command button is on the parent form. In this case it would be: Me!Subform1.Form!ControlName

TextBox1 + TextBox2 + $0.01 :p What happens if you set decimals to 2? Try setting the decimals to 2 in the form and table as well. What is the value in the tables? Perhaps your error is not in the report?