Recent content by delikedi

You could use DoCmd.ShowToolbar "Ribbon", acToolbarNo somewhere during initialization. BTW, if your users have only the "runtime" version of access installed, you would have to distribute the accde version of your app anyway, and the ribbon would automatically disappear.

Oh ok then :)

When the line Debug.Print strSQL executes, you should see something like in the immediate window, assuming that the fields "Action" and "Comments" are of string data type (you do not have to user double quotes for numeric data types). The problems I see with your version is the lack of...

You are attempting to use the variables directly inside the SQL statement. The SQL interpreter cannot distinguish that strAction is in fact a variable and read its value. You have to concatenate the values those variables hold to the SQL statement manually: strSQL = "INSERT INTO tblBackupLog (...

When changing the value of a control programmatically, events of that control do not fire, as opposed to the fact that they do when the change is manual. That's just the way it is. Therefore you have to call the procedure explicitly. Call ctlChosenClient_AfterUpdate immediately after you modify...

Thank you for your thorough answer. I've come to better realize that a relational database is actually a translation of a real life system into a virtual system. Your notion that a database should be platform-agnostic makes a lot of sense. The platform and/or the application that manipulates...

I've been developing a database that I created from scratch, with a large number of entities and numerous vba procedures in it, for a while now. I've become comfortable with the concept of normalized database design and also with writing procedural VBA code. I believe I understand the basic...

I've started using VBA and Access simultaneously, about a year ago, due to a project I was tasked to do. The project was about a database, but it evolved a lot very fast, into a departmental application. Along the line, I shifted to use unbound forms because I found myself unable to do some...

I receive the same error in IE. I don't receive it in Firefox though. The error happens when you want to navigate to the site.

Considering you only have a handful of queries, it may be more practical for you to keep up your current way of doing things rather than implement this solution. I have developed this solution around the time when - I had nothing more to learn about concatenating sql in vba code - I found my...

And here's my code for the main and complementary functions. Error handling is left to the user. The main function is named GSQL, and the others are for ensuring that the data is SQL compatible. Public Function GSQL(ByRef lngStatementID As Long, ParamArray varParams() As Variant) As String...

Sure, I'd like to share my version. This technique practically eliminates the need to construct any SQL statement using VBA code forever, so I'm sure many people have developed their own version of it in one way or another. For this technique to work, I use the following table: zstblSQL...

Try if Dlookup("[ItemsRemaining]",[qryClientCourseItemsRemaining], "ItemsID = " & [Forms]![frmDeparturesPaymentScreen-ItemListSubForm]![ItemsID])

Constructing SQL statements in VBA can become very tiresome and time-consuming. A better way would be using a "sql statements" table. That table would hold the ID number of the statement, the statement itself and the number of parameters (if any) to pass to the statement. After establishing the...

I'd like to offer my solution as an alternative. I use a table that resides in the front-end of the application. I use this table instead of global variables, so the table has as many columns as the global variables it replaces. The table always has just one record. During login, that record is...