Search results

In the early days I started with Access2.0 to build a database for my coin collection. I had some experience with VisualBasic on a Commodore, and had followed a course in Pascal, so the step to Access was not to difficult. But going along I experienced the programming as copy-paste, copy-paste...

Hi Dalski, I don't use composite keys. When I am in my "new record"-form, and the user wants to store it, a couple of checks are done. One is are all obligated controls. If not, no save, and return to the "new record"-form. The same holds for all kind of other conditions (too many characters...

No, never persuaded. But I did feel why they were asking something that they could handle, and understandable for them. Especially older people, or not technical skilled, don't think in normalized data. And thus are not always happy with the way structured programs work. But this brings me to a...

I am not sure, but I think all your goals are already implemented in my applications. But be careful, it is a complete different look at Access. Instead of starting with the data-structures, it is starting with the user-definitions. Let's start with some simple remarks, that will probably start...

In a certain niche MVF's can be useful. But when continuing on generalization, to make forms independant of the user content, I am afraid they work in the wrong direction.

In my opinion the problem is that the behaviour of all controls are based on the type of the field, or, in the way the data is stored. But Usercontrols are more than that: the way a user wants to influence the control. That is why MS added BeforeUpdate and AfterUpdate events, input formats, and...

Probably every developper has build some code- or object-library for fast and robust developping of applications. Most are general error handling, form classes, control classes, ... Some 40 years I am playing with generalization of Access applications. The problem (or my problem) with Access is...

I use the above idea to "view" a report, if it is in its final stage. Left you see a column "Controles", with 7 checks. When not ALL checks have succesfully passed (backcolor is green), the report on the right will show the red text. In your case you could use the pressing of the Print button...

What is the difference between a Access form control and a 'real' Windows control? The kind of binding?

"By accident" I read the above line. I am working on a project where I have completely decoupled front-end from back-end. I only work with local applications, no SQL-server. That could make a difference. The problem with the coupling of Access is that Access starts from the Fields. You than...

OK, I understand. The only thing the As_xxx functions do, is to convert control-values (that are formatted according regional settings), are converted to native types. That is all.

Well, interestingly. Can you elaborate on that? Thank you.

Hi John, Thank you. These codes are some 40 years old, and I have never found a signal that there was something missing. But adept them for your purposes. Your example was for retrieving records based on field-values, and in the tables I don't use ZLS-values. Internally I work with controls...

Place these functions in a general module. Modify/extend these functions if necessary. Function As_date(cur_datum As Variant) As String ' ISO-format: yyyy-mm-dd If (IsNull(cur_datum)) Then As_date = "Null" Else As_date = "#" & Format(cur_datum, "yyyy-mm-dd") & "#" End If End...

An other frustation in constructing SQL-strings is the type-dependant notation of variables: single quotes for Text, # for Date, decimal point for Real values (dependant on regional settings). I use three simple general functions that I use everywhere: As_text, As_date, As_real, independant of...

Beware! vbKeyDelete = 46 vbKeyPrint = 42 Did you really test for "ctl del"? Perhaps better to use the Constant vbKeyDelete.

In your code you use: KeyCode = 42 & Shift = 2 & is for concatenation, better use AND: (KeyCode = 42) AND (Shift = 2)

You could make your life much easier by using a little different typography. Most important is the leading space in each line, very easy to check if each line has (or needs) such a space. Public Sub inToDisc(dFamily As String, sFamily As String, nAccno As Double, sStr As String)...

First of all, I would ALWAYS split the database in FE and BE, because modifications of the FE will come sooner (or later). The user does not even know/care that the database is splitted. I was interested in your application, not so much the code, but the systematics. I always compare that with...

What if you make a recordset with flocID = ID AND DocID = ...? If (rst.EOF) Then rst.AddNew Else rst.Edit End If