Search results

Ken, that was the general idea! You don't need the eval() in the code module in this case. I'm not sure exactly why you have to have it with recordsets that use queries that reference form controls. I have seen ana explanation but it escapes me now. It also has some other odd uses: It allows...

Ken, In my first post I was saying that eval() was intended to be put into the original query. It does not contribute much in a code module, in this circumstance. Chris

If the SELECT section of the INSERT statemnet generates more than 1 record, then you have a problem because, as you feared the DMAX statement is only executed once. Unfortunately, I'm not exactly sure what you are trying to do. Is job_process_count for dbo_operations_template an autonumber...

Dcrake's idea is good. If you explicitly state the form's name in the Close statement, then you can be sure that it is that form that Access is trying to close. I vaguely remember hainv this problem myself and discovered Access was closing something else. The solution was to add the formname to...

Why not just try it on in a development/test area?

hi again, if you want to create the SQL string in a code module, the following code is copied from KenHigg, except for the fact there is a single quote jsut before the first asterisk and just after the second asterisk. strSQL = "SELECT tblPlants.[Botanical Name], " & _...

Fearoffours, using eval() almost always solves this. It works within the query definition, e.g put the following in the criteria for the Botanical Name field in qryPlantFromPlantsForm: like "*" & eval("[Forms]![frmPlants].[txtFilterName]") & "*" HTH, Chris

Aziz, put the following into a VBscript file - obviously substituting the dummy names for you own: Dim db Dim strDbName dim strPassword dim strMacro strMacro = "YourMacro" strdbName = "c:\yourpath\yourDB.mdb" strPassword = "YourPassword" Set acc =...

Why do you have 2 frontends? I assume the first frontend must do some sort of look up which verifies the user's security, which in turn opens the 2nd front end. If that is the case, why not just have the lookup in the 2nd front-end and remove the password protection. as you have disabled the...

try: DLookup("[Total Hours]", "TimeCard", "[Employee]=" & "'" & [employeeTextBox] & "'" & " AND [Job Date] =" & clng([tuesdaytxt2])) this works if the tuesdaytxt2 is formatted as a date not a string HTH, Chris

What is the situation, exactly? Your explanation is quite vague, how ever obvious it is to you, we have no context. Do you mean that you want to send a message to a PC over the network that says I want the user out of Access in say 10 minutes? Or do you mean, the user has a set amount of time to...

What is the situation, exactly? Your explanation is quite vague, how ever obvious it is to you, we have no context. Do you mean that you want to send a message to a PC over the network that says I want the user out of Access in say 10 minutes? Or do you mean, the user has a set amount of time to...

If you are not sure how to run code when the application closes, you need to create a blank form and put the connection closing code in the unload event, then open this form in the hidden state when the application opens. When the db closes, the hidden form will be unloaded, thus executing the...

hi, the fact that it is a bit slow is probably because the database is on a network drive. How fast is the network normally? There is nothing wrong with your code. To speed things up you could make objCon as public variable and put the following code in a module and have OpenDB called by the...

you may find this link interesting, especially the middle bit about VBA applications HTH, Chris

Try: todaysdate = Date() HTH, Chris

You need to add a reference to the Microsoft Office x.x Object Library (where x.x) is the version number.

If I remember rightly you cannot use this syntax to change the security of the current Access database, it used for opening another database from within the current one, using the Workgroup stated in in the DBEngine.systemDB = "..." command.

Microsoft says in its DAO reference documentation: "For this option to have any effect, you must set the SystemDB property before your application initializes the DBEngine(that is, before creating an instance of any other DAO object). The scope of this setting is limited to your application and...

The quick answer Sven is to make the procedure public instead of private, e.g. Public Sub OpzoekenMoederrolGegevens(Optional dMoederrolnummer As Double) and call it with Call forms("FrmIngaveParameters").OpzoekenMoederrolGegevens(Me.txtmoederrolnummer) However, I'm not sure what you are...