Search results

I want to be able identify certain tables, and then run actions using only those tables. How do I do this? Background: I have a database of checklists. They want to use this to make sure they follow consistent and complete procedures on different types or projects, and to track the progress...

Gina & Dave/Gemma, I've tried form.requery with no luck. That leads me to what Gina said, although I don't understand why a requery doesn't do the same thing as a close and reopen. However, that doesn't explain why the update (both refresh and requery) works for one field. Yes, it is an...

Gina, That's good to know. However, why does it update on one field? Now what? 1) I could try to make it an updateable query. I think to do that, I'd have to put the one field that makes it nonupdateable (left/right join) into a sub form. 2) I could call a module that closes, then...

It'll take some work to do that. Let me think about it a bit to see if it's worth the time. What I don't understand is that the update works when changing one field, either refresh or requery, but not on others, despite the same code (public sub). Could the form be corrupted? If so, do I...

Been there. Done that. No luck. tID = Me.ParentID Form.Requery DoCmd.GoToControl "ParentID" DoCmd.FindRecord tID

I have a form based on a non-udateable query. To change data in a field, I click on the field. It makes visible an unbound combo box, and assigns the underlying value to that combo box (Me.cmbSID = Me.SID), and shifts focus to that box. AfterUpdate changes the value in the underlying table...

First, it's hard to offend me. Be direct. Second, I know what I know about Access. I know what I don't know. Lack of knowledge in one area doesn't necessarily imply lack of knowledge in another. I've used rs successfully to do actions in other areas. I was trying something new. It didn't...

Mark: Phew indeed. You should've seen it before I took it over. I did a lot of normalization. Now I'm doing some unnormalizing for efficiency. JDraw: They want to see 3 years worth of history, so that's what I'm giving them. Anything >36 months falls off.

Just sayin' I get it. Sometimes an efficient table structure isn't efficient for processing. The 1-36 fields represents 3 years of monthly data. I bring the data into an efficient, vertical table (ID, date, rev, tran). Then, I translate this into a horizontal table (LastDate, ID, rev1...

Overthinking? Me? I resemble that remark. :) I try to learn the underlying reasoning and inner workings when I can so that I can apply concepts to a wide range of things rather than just solving the proximate issue. I've heard it's best to minimize stored queries. What you're telling me is...

Let's go back to my original question. What's the best way to open a select query for viewing without using a stored, named query? Related to that, is this something good to do, or should I just store the queries? My thought is that fewer stored queries means a smaller front end. Is that so? If...

My intent is to open select queries without having to store it as a named query. docmd.RunSQL only works with action queries. docmd.OpenQuery only works with named queries.

I already found and fixed the extra space in Tran35 and still got that error message. Any other ideas?

I am aware. I'm not including all of the fields. I haven't found a non-existing, misspelled field. I copied the sql from a working query, and copied it back to a new query to test, and it worked. Could it be that the string length is too long? My hope in doing this it to cut down on...

What's the best (or another) way? When I try below, I get error #3061, Too few parameters. Expected 1, on the line highlighted. Dim rs As DAO.Recordset Dim stSQL As String stSQL = "SELECT qryRevTranBiller.BillerName, qryRevTranBiller.ClientID, qryRevTranBiller.Prod...

The other problem still occurs, "Run-time error '1004' Method 'Save' or object '_Application' failed" on the line "x1App.Save" Abbreviated code: Dim stQryName, stFilePath, stFileName, stClient, stFileDate As String Dim xlApp As Excel.Application Dim xlDoc As Excel.Workbook Dim xlSheet As...

Upgrading to Access 2013 fixed the email problem. IT couldn't fix it by either the Run as Admin method or trying to fix registries. I couldn't fix it by adding libraries. So, they upgraded me to 2013 early. Sometimes it pays to complain. :)

Yes, they are the same. Others checked: VB for Applications OLE Automation Microsoft ActiveX Data Objects 2.8 Library Microsoft ADO Ext. 2.8 for DDL and Security I've been told I don't need both ActiveX and ADO, but don't understand which one I should keep. Nothing shows as missing...

References checked include: Microsoft Access 14.0 Object Library Microsoft Office 15.0 access database Engine Object Microsoft Outlook 15.0 Object Library Microsoft Excel 15.0 Object Library

It's Microsoft Outlook 2013, part of Microsoft Office 365 ProPlus