Search results

Interesting... After looking into that - it seems those errors were there only due to issues while I was setting it up. It now seems to work without generating any new errors... I ended up adding a command in the back-end code that runs a query in the front-end that modifies that table - thus...

Yes - a timer is another way to go - but I was trying to avoid that and have it actually event-triggered.

I'll have to chew on that. I guess it is indeed another anomaly of this approach - as it will always be in a state of "having-been-connected" to someone's front-end. But since I'm expecting that to be quite static (essentially one person under normal circumstances) it seemed at least OK to do...

Actually - there is only one Data Macro and it resides in the front-end. I figured it best to get it working in the isolated front-end area first - which it does. Then in the BE, I linked to the FE message table. The hope is to have BE code be able to make changes to that FE message table and...

In the attached, there are a couple database files, one is for FE and one for BE. Note that they only contain what is necessary for this question - so they don't even have any of the usual data tables that would be in the back-end. So I know it looks reversed, but that just happens to be what...

@jdraw - I will see if I can quickly gin up a couple files - but was hoping that the explanation of the code might be sufficient. @theDBguy - All of what I described is in the front-end and it works when changes are made within the front-end. What I have is a back-end database that links to...

In my table (called tabFEMessages) I have set up a RunDataMacro on the After Update, that calls a Data Macro named "tabFEMessages.dmUpdateStatusMessage. The Data Macro has only one command in it: SetLocalVar Name varStatus Expression = UpdateStatus([StatusMessage]) Where "UpdateStatus" is my...

I do have the system set up in the normal way - with shared data in the back-end etc. etc. Most users will be doing the usual 'thing', running queries and generating their own output etc., based on data in the shared tables. But one user will be managing the input to this system, and this was...

Yeah- I agree - it is indeed weird. I don't even really like it since the back-end is linking to a table in the front-end. But since I know I'll have only one Admin - or certainly only one Admin at a time, it seemed OK to have the back-end reach back and link to the front-end for this purpose...

Hi jdraw - thanks for asking... Yes - it is a split database, and normally you have the linkages from front-end to back-end tables. In this case, I have a bunch of code in the back-end that updates the shared data, but I was trying to keep all users connected via the front-end, including the...

I'm trying to use "data macros" as a basis for performing a trigger-like action in Access (365). Ordinarily I might do this simply with an "After Update" event on the field of interest with some VBA etc., but in this case, I have a split database, where code is running in the back-end, and I'm...

This is for bad jokes? OK: . . . Q: Why does a giraffe have such a long neck? . . . . . . . . . . A: Because it is so far from its head to its body.

I'm just glad it was easy and hopefully I updated it fast enough so that I didn't waste anyone's time.... good grief...

Sorry - I posted too soon ---- I figured it out. It was because I had code in the Load event that updated the recordsource to a DIFFERENT query - but only in that one form. Oops. So never mind... ;)

I have two forms, both of which I've updated the data source to a new query - and both are presenting the exact same new field from that exact same query... One form works fine, the other shows "#Name?". I've double-checked the field name is correct. The two forms are both of the same type -...

Indeed ---- ;-) I just ran into a problem - we'll see if I can figure out where/how to post it...

@pbaldy, @isladogs— yes, it worked... good to know... thanks!

Thanks all! So - dumb question - do you use the "@" prefix to refer to usernames - or is that not used here?

Here's a possibility - maybe: Query 1 (qryTest1) written as such: SELECT T.[Partners Name] AS Partners, Max(T.[Comment Date]) AS Comment_Date FROM [Any Table] AS T GROUP BY T.[Partners Name]; With Query 2 written to use qryTest1 - to give your intended outcome: SELECT Q.Partners...

theDBguy is spot on... I will often do a dim strSQL as String, and then set that variable to the string that defines the query. You would then have ...OpenRecordset(strSQL) instead. I would then pause the code at that point, use the "View Immediate" screen, and type ?strSQL in it - to grab...