Recent content by MarkK

You are performing business logic AND user interface logic in the same routine. Generally you should isolate both. The hazard of not isolating them are... • If you refactor SQL_Delete() or the refresh methods of the Form, this routine will break without warning. • If your system continues to...

I read your post. I know nothing about your problem, except that it involves links to pdf files. Cheers,

You could do... Const Q_NAMES As String = _ "OrphanAddCharges " & _ "OrphanDaily " & _ "OrphanAddChargesInter " & _ "DeletedHorseDetails " & _ "DeleteDupHorseID " & _ "DeleteNoHorseID " & _ "DeleteInvoice " & _...

Interesting observation. I certainly go to AI first these days...

Glad to hear it, thanks George. Looking forward to hacking this line of code... Private Const MAX_WIDTH = 22 * 1440 ...out of a bunch of forms.

Sorry, I meant extensibility, not scalability. Tight-coupling defeats extensibility.

For a contiguous range of dates you only need the start and the end. This could be implemented using just two navigable month view calendars, one for each data point.

Finding the date and moving the view will likely be two steps. 1) Find the row you want to highlight 2) Move the record pointer x number of rows to scroll the view so your selected row is where you want it. 3) Re-select the found row to highlight.

Tight-coupling defeats scalability. They are inversely proportional.

Maybe not exactly to your point, but I wouldn't link to a table just to get one field. A link is a necessary evil, a data point you create in order to support a relationship between entities, but if the related entity is itself only one data point, omg, just put that data directly in the object...

True, but the calling form knows about the popup, and explicitly references its named members, so this is still a tightly coupled approach. To improve this, the popup might implement an interface, and then the calling form can reference the interface. Then they would be more truly agnostic...

Here's a simple way you can communicate between objects in an application without them knowing anything about each other. This example passes a command button and a string to a form opened with the acDialog switch, after it opens, from the form that opened it. To run the sample, open the fTest...

I would not do such a conversion. Trading time for value, I would get going in TwinBasic--which supports DAO anyway--long before I would convert an exiting DAO application to ADO.

This is a statement by a person about herself. This is not a statement about OOP. Everything you do as a programmer is underpinned by OOP. You may not write classes, but the context in which you write code and every resource your code consumes is a class, and is exposed by a class. Any action...

I write a service class for almost any information domain in an application. The service class takes responsibility for all business logic in respect to a particular domain. Any and all business logic--exactly like the kind of thing you are talking about, where if one date is advanced, a second...