Search results

Thanks. This works, in that it now returns the date spread that I want. However, although I put the same format on datStartDate and datEndDate, the msgbox returns 30/04/2019 (UK format) on datStartDate and 05/01/2020 (US format) on datEndDate It works, but it sort of still doesn't, but it does...

I live in the UK and use dd/mm/yyyy I have the following code to select records for that fall within a financial year (1st May - 30th April) Case 2 datStartDate1 = DateSerial(Switch(Month(Date) > 4, Year(Date), True, Year(Date) - 1), 4, 30) datEndDate1...

I used to have an access "web database", which was located on my Office365 account. That system was rubbish. Only allowed the use of macros, apart from anything else, no VBA. That's why I replaced it with the current Sharepoint List BE / Access FE that I have now.

I'm really confused now. I have a database that uses lists on sharepoint as the backend via office365 using access for local frontend copies. Seems to be working as it should.

Hmm. That's a bit alarming. Especially, since we've been using it for about 6 years and haven't noticed any problems... Then again, it's only half a dozen users with a fairly small likelihood of any of them being logged on the db at the same time (however, that said, there have been...

Ooo, ok, I can see a use for that right away. I have a button that adds a new order to one table and then immediately adds an invoice with that order number to another. Currently I do this: With RS1 . addnew ! [fill the fields] .update .movelast intOrderID =...

Thanks. That's what I have done, although I put the sql in a string first, because I was feeling fancy...

Wow! That's complicated looking stuff :eek: I started looking through it, thinking, "OK, I sort of see what you're doing here..." Until I got to the bit where it says "Set rst = db.OpenRecordset("SELECT @@Identity". What??? @ signs?? Where did @ signs come from? You're just making stuff up...

I have a query to delete some records on the click of a button. Private Sub cmdUnmark_Click() DoCmd.OpenQuery ("qryUnmarkUser") CurrentDb.Execute "qryUnmarkUser", dbFailOnError MsgBox "Records Unmarked" End Sub (I use one option or the other, not both) If use the DoCmd line, the query...

Yes, that seems to do the job. I will have to dissect it to see how I can splice it into mine, but I think it should be what I need. Many thanks. George

My experience with FE/BE databases has been with using the BE on sharepoint. Changing the FE and sending new copies to users is a doddle, because the sharepoint links remain the same wherever you are But, if you design a FE/BE db for someone and install it on a server at their location, how do...

Does anyone know if you can get Access to print one label to a specific place on the label sheet, like you can in word (eg: 3rd row down, 2nd column accross)? Obviously, one could export the data to word to do it, but that's less convenient.

Thanks. My plan was that whenever the user has completed whatever they marked the records for, they would click the button to "unmark all", which will delete the relevant records in tblMarked, so I don't think there should be a need for a date. It will lead to a lot of creating and deleting...

6 users, all in the same building, so it shouldn't be a problem to make sure that everyone is signed off, hopefully.

So Gassman's suggestion of replacing chkMark with a fldUserID might be a better approach (allowing more than one userID per field by use of a delimiter?)? As an aside, is there any risk to compacting and repairing "too often"?

I think that's the approach that I was trying to portray in the OP. MajP has suggested that constant adding and deleting records in the BackEnd could be problematical, though (although, it's a pretty small db). It's all theory to you??? It's incomprehensible arcane lore to me!!! :confused:

Ooo. Hadn't thought of that option. Interesting. Initial reaction is that I can foresee a case or two where one user might want to let another user see their marked set, which might be more complicated with a local marked table? No clue about how many actions, how quickly are needed to cause...

Add a "UserId" field to the Contacts table, you mean? The problem with that is that two users might want to mark the same person at the same time for different reasons. (Eg: one user might mark a small batch of users for personal contact reasons that she might want to keep marked for a few...

In the past, my db has tended only to be used by one person at a time. So when a user wants to mark a group of contact records to be dealt with for some reason, I have just had a "fldMark" checkbox field on each record that the user can check either individually on the forms or in groups by...

It tends to be that no matter how small they are, they think that Access is for smaller. Most of the people I have been talking to have been talking about thousands of records, tens of thousands at most - so I would have thought that scale would have been a problem. I'm working on learning...