Search results

Hi To be honest, it was barely clear what the OP was wanting based on the initial question :-p. Can you describe exactly what it is you're trying to achieve? (And, it'd really be best offered as a new question thread. By all means post a link to that thread here.) Cheers

This is sad news indeed. I've barely had time to post in one forum lately, so have missed out on continuing interactions with Chris in recent times. He was always wonderfully invested in exploring and advancing Access development. It's reassuring to think how those many offerings over the...

To be honest, I've never been one to berate MS for not including things that can be achieved by other means (even if they subjectively feel convoluted). I've always wanted more things that can't be so accomplished - which, alas, have been thin on the ground in recent times. On the topic of...

The UI aspect being part of why it should have made some difference. (Even if not tangible - and certainly not noticeable compared to adding a PK index :p)

>> As soon as I defined the identity column as a Primary key, (and SQL Server added the implicit index) performance increased massively. The sort of thing that we'd have assumed as already being in place. Yes - a massive, massive issue and inevitable difference. It explains everything. (I...

That's a lot, but I'm assuming you don't use them all in any given application. ;-)

Can I suggest that you use the form's RecordsetClone, rather than the recordset itself. (Or at least a clone of the recordset.) i.e. Set rs = mapto_subform.Form.RecordsetClone or Set rs = mapto_subform.Form.Recordset.Clone It won't necessarily shave much off the execution time (though should...

Underwhelming, to describe the buiilt-in button icons, is being a bit kind. :-p But that doesn't prevent you from being able to assign your own images to a control, and *then* store them in a binary table as described - or even the form based method just described. Some reasons? Portability...

You don't need another table per se. That's just the most flexible solution without requiring certain UI elements. But the process of assigning the PictureData property remains. Instead of a table, some might choose to have a form, which remains open throughout the application instance (but...

I'm afraid I'm not at all clear on what you mean by that - but you seem to be OK running with it, so that's good. :)

Though it's not a particularly rigorous or efficient suggestion, it does circumvent the (as you observed) undesirable practice of storing a calculated value in your invoice table... You could just use a DLookup into a field to allow display of the sum value from a query while maintaining the...

Hi I'm not entirely sure what to suggest, as I can't be sure what your problems are. If you want to know how much has been banked... then is that not as simple as a field on the receipt indicating if that amount has been banked? (A boolean field even.) Or, in the case of cash, if part of it...

Are you only associating clients with orders through the OrderCards table? i.e. you no longer have a ClientID FK in the Orders table? Again that seems escessive (as it requires the existence of OrderCard records as an order is created). If it the ClientID FK still present, then that is your...

Indeed. Can't beat a good set of naming conventions. ;-)

Agreed really. But, FWIW (as mentioned elsewhere) Call Forms("frmTrimData").lblTableName_DblClick(False) Unless you do want to cancel the event for some reason. :-p

Hi. To be fair, ADO should be perfectly safe enough, especially in the context of this question. It's not being deprecated. Only the OLEDB provider for SQL Server is going to be (and that's starting with the next version of SQL Server - yet to come).

Sorry for the delay on this... A few general items without pouring over this... >> Me.cboSmartSearch.RowSourceType = "Table/Query" Don't assign this property. It's a) redundant and b) not a property you should try to set at runtime anyway. (It can cause requerying issues.) >> 1) Conceal...

So it is reasonable that you can associate a card with a client, without them requiring an order first? If so, then yes - there's no issue about it. The apparent circular reference isn't that - as the business rules dictate that a client must be associable to a card without the need of an...

Just a brief point... Your assertion is that you're not returning records. That's not true. You've tested both BOF and EOF and they're false. You have records returned. The RecordCount property returning -1 and you getting records returned are two different things. In this case, you're...

Presumably the combo's type during development is already "Table/Query"? Specifying that is unnecessary. Given that you're setting the RowSource property, then calling the Requery method is redundant. (By setting that, you've already requeried it.) Do you not see the results you want...