Search results

Could you just come up with a disposable FE DB and restart the entire FE application "every 90 seconds"? Not sure since in my design I do not leave any QueryDef objects in the DB long term. So I do not know if Access leaves a lingering connection as long as the QueryDef object remains in the...

Previously to present time, I used to have one ADO Connection object which was passed by reference from an application global object. If the connection would ever drop to the SQL BE DB, it would never reconnect. Windows 7 has a more severe power save than Windows XP, and was toasting the ADO...

:eek: PEOPLE!!!! :banghead: Nothing like putt'n the K in Quality!

According to this page: http://office.microsoft.com/en-us/access-help/HV080753695.aspx That constant is only supported for "Microsoft Access workspaces". Here is a snippet of my code which creates a DAO.QueryDef in Pass-Through mode. Dim daoDB As DAO.Database Dim daoQDFbe As DAO.QueryDef...

The way to keep formatting is to: 1) Create a empty spreadsheet with all of the formatting in place 2) In Access VBA, make a copy of that template file to the target filename (I use the MSO SaveAs dialog box to accept a target filename), and make a copy of the template to that filename 3) Then...

Sounds like you have an issue between the Windows client and new server, since both drivers give error messages connecting to the new server.

Let me tell back to you what I perceive your configuration to be, and you confirm the correctness... 1) Windows XP OS 2) Access 2000 3) Back end DB was SQL Server 2000 4) Back end DB needs to become SQL Server 2008 R2 Correct? If so, what driver was the application using successfully to...

Are the queries logged somewhere? Are they plain SQL? You could use a SQL GROUP BY query to organize the data by the type of query, then within that query place a COUNT(*) AS [count] to count up how many in each group... that is, each type of query executed.

Must the manipulations be done in Form1 code? Or could Form99 check for an OpenArg and itself know what it should do based on who opened it? Form1 to open, then reach in and modify Form99 is exactly what I have been coding this afternoon. That is fairly advanced VBA, opening forms via their...

I just thought to check again and found the Wiki presently working. Thank you.

I assume you mean that you have an unbound text field control, yes? You will need to safely read that text field control, so see this post: Safely read form field text controls http://www.access-programmers.co.uk/forums/showthread.php?p=1131039#post1131115 Once read into a VBA string...

SetFocus rather than Focus perhaps?

Right there looks like an issue. So where did you put this code? On that form itself? If so, refer to it with Me instead. Example: rs("Child Name").Value = Me.enrollchild_childname.ValueAlso, to safely read form controls, I developed a bit of shared code which gets placed in a separate VBA...

99% of my use of SQL in Access is fully spelled out SQL statements. This SQL Filter as you call it is in the 1% of my development work. Thus my lack of familiarity with the subtle ensconces. As you stated, there is one with ADO objects. ;)

Perhaps attach a screen shot, please.

No, the subform has no general awareness of the mainform controls. Besides, the scroll bar is for only the subform, correct? I do not follow your thinking to SetFocus to a control on the main form in hopes that the subform will scroll up.

The only way I know to force the scroll bar is to send SetFocus to a control, and doing so causes the scroll bar to follow the focus.

I believe Access is trying to position the subform scroll bar to allow visibility to what ever control on the subform initially has focus. Do you have a control near the top of the subform which you could either: 1) Make the first control in the Tab Stop list or 2) In the Load event of the...

rrrr???? This is not a complete SQL, it is only the WHERE clause of the SQL: 'Atttach to the Form's record set Set daoRS = Me.RecordsetClone strWhereClause = "[" & strFindInCol & "] LIKE " & Chr(34) & "*" & strFindText & "*" & Chr(34) If flgFindNext = True Then daoRS.FindNext...

I was more testing the waters of what I am thinking to do. I coded it up today. It appears to work the way I think it should. The DAO.Recordsource is just an odd beast in that it accepts a SQL fragment, not the complete SQL. So I was wondering perhaps in the neutering process, MS disabled...