Search results

The INSERT INTO solution seems to work well... *if* performance isn't an issue. I was copying each field value individually, and tried replacing it with this more generic solution. The functionality is correct, but unfortunately, my 30 minute task now takes over 24 hours to run.

Well, I'll remove the DoCmd.Save from my production code and keep my fingers crossed!

Thank you boblarson! I do have one question. If I add DoCmd.Save to my y_Click routine above (where I intentionally try to break it), it still doesn't seem to be putting y in the property sheet. Any idea why that would be? I would love to be able to intentionally reproduce the problem.

Yes, I do have a DoCmd.Save. Could that really be the problem? In the past I've questioned why the command is in the code. A while ago I even added the following comment: DoCmd.Save ' If BeforeUpdate called us, it should save anyway, no? I thought the command was superfluous, but it never...

Here's my nightmare. I'm doing development on a large Access program (lots of VBA). One day I open the Access file and my forms are completely messed up. Property sheet values have changed everywhere... in the forms themselves and also in the controls. Actually this has happened several...

Solved! Thank you Dennisk! Coincidentally, I ended up implementing the same last night -- and it worked! Well, it wasn't exactly the same..... I took my code pretty much straight from http://support.microsoft.com/kb/q129796/. The one difference is Microsoft's version is a Function, and it...

DJkarl, Thanks, but the problem is not with the database. It's with the VBA. My DOS commands (and perhaps DoCmd) are being executed asynchronously, or so it would appear. This is really stumping me. Any help would be appreciated!

I'm trying to write to a file using a combination of DoCmd.TransferText (to a temp file) and DOS commands. Problem is, the lines are getting written out of order! Here's a snippet (this is actually part of a loop): strCmd = "cmd /c echo " & strHdr & " >> " & strPath Shell (strCmd)...

systemx, did you come up with (or choose) a solution? I have the same issue, and am seeking a programmatic fix. (Note: Late binding seem like a last resort solution; I support tens of thousands of lines of VBA, and can't imagine that conversion to late binding would be simple....)

Did you confirm that the Access 2003 user who is NOT experiencing this problem is also on version (11.8166.8172) SP3? I have an Access ADP (SQL Server back end) thast is crashing on this version only.

dadigu, It's been a while (I'd have to dig through my deltas), but I think I did basically this: Private Sub Form_BeforeUpdate(Cancel As Integer) If Me.Dirty Then Me.txtLastModifiedBy = GetUserName() Me.txtLastModifiedDate = Now End If End Sub In the subform: Private Sub...

Problem Solved! The AfterUpdate/BeforeUpdate solution proposed by dc.gypsy actually fixed the problem, and I was able to remove my hideous kludge! Thank you dc.gypsy, wherever you are! Thanks also to peej228 for the alert on the timestamp. Though that isn't the culprit in this case, this is...

I believe I have solved the problem. Turns out to have been a dumb user error (said user having initials YT*). The code didn't actually disappear; it was never ported to production. Since there was no schema change, I was a bit cavalier about changing the connection string in Access. Forgot...

[Note: This pertains to an Access Data Project (ADP).] I modified a stored procedure on SQL Server, and later discovered that my changes had disappeared. I'm wondering if there's any possiblity that my Access ADP might have been the culprit. I would think the answer is no. When I open an ADP...

Thank you to dc.gypsy for the reply. I cannot remember if I tried that AfterUpdate/BeforeUpdate combination or not. I have had to put this tool on hold (my company won't let me work on it until it gets rebudgeted -- funny how that works), but will try it out as soon as I can. If anybody else...

Oh, maybe I wasn't clear. When I said the tool broke, I was referring to my original post (per the preceding paragraph). This is the one you originally responded to. In other words, I was saying the "record changed by another user" problem (that you and I both experienced) caused my tool to...

I did attempt that route, and in fact started another thread on it. As you can see, I ran into a dead end here also.

Unfortunately, I have received no assistance on this, and have found nothing on the web. So... I am still living with the "horrible solution" I mentioned. I do need to look into this some more, as the users are getting extra message boxes as a result of the increased event firing -- rather...

acCmdSaveRecord Hmmm, that's close. The acCmdSaveRecord is called inside Form_Error which is hit between the BeforeUpdate and the AfterUpdate events. So that would pretty much be the Update itself(?). For what it's worth, we're using ADO w/ a SQL Server back end. You have been kind to...

acCmdSaveRecord Thanks, I appreciate the response! Good info. I couldn't fool it though. When that line of code gets hit, I get "Run-time error '2115': The macro or function set to the BeforeUpdate or ValidationRule property for this field is preventing the tool from saving the data in the...