Search results

Can you import the db into a fresh new database, then try. Rebooting will/should release any lock. Is there a lock file showing?

Totally agree. I've had all sorts of fun and games with legacy systems we've started to look after where formats applied at table level hide the true values being stored and then wondering why we were getting rounding errors. As others have said - formatting should only be for display purposes.

In addition to Sonic8's suggestion, don't reset the combo box row source to default every time if it doesn't need it to be reset. You can check if it's already in the default state using something like. If Len(sText) < 3 AND Me.cmbIngredient.RowSource <> "SELECT IngredientID, IngredientNew...

If the ^{F4} is designed to close the access app after it has "done it's thing" there are much better ways of achieving that. You could simply put an Application.Quit into the VBA in the Access database. If not I don't understand it's purpose? Have you tried commenting it out. I would simply...

Put a Stop or MsgBox command in the VBA in frmDone, and see when and if it fires. Doesn't ^{F4} send a close command to the active window or am misinterpreting that?

Make sure the parameters are explicitly defined in the source query.

To make this work efficiently I would suggest you create a calendar table, ( Ideas for it here ) and then you can easily create a query to join your clock table to the available dates and find the last calendar date that doesn't have matching record and then count the days / hours they did work...

@DDJKSA I hope you appreciate the difference in how the data is stored to make the queries work able? This is why Normalisation is important. Kudos to @arnelgp for taking your data and manoeuvring into a sensible format.

I was driving past the local prison yesterday and I saw a dwarf shimmying down the wall using knotted bed sheets. I thought to myself "That's a little condescending".

I'm on a O365 subscription, and refuse to use the new Outlook, it's awful by comparison.

You can't point that at one candidate without some balance: It's an important issue, obviously.

Unfortunately it really does matter. What happens when you add a week or period to your current structure? You would have to rebuild the query you wrote. Currently your query will be absolutely horrible , something like SELECT Sum(CountC1) as XTotals FROM ( SELECT Iif(C1 = "x",1,0) as CountC1...

I'm afraid your table sounds like it is designed like a spreadsheet, so this will be very awkward in Access. You tables should be long and thin with fields along the lines of Subject, Period, WeekDay (or possibly simply ClassDate) You then can simply add up the data by column and subject.

I don't think you can dim sf1 as a control then try and set it a form reference? Shouldn't it be Dim sf1 as Form Unless sf1 is a subform control, and not the form itself ?

We did, very quickly afterwards you wrote in post #5: Read carefully the last line that YOU WROTE , dismissing any reference to any existing applications, experience, or what it was you were doing that would involve adding dozens of objects every month. We asked, you diverted. We asked...

You can only create a finite amount of objects on forms, including any that are deleted. This is therefore not recommended under any circumstances, in addition you can't make design changes in a compiled ACCDE version of any Access application, so "on the Fly" changes are a no-no.

If only you had written this to start with we would have known exactly what you wanted to find out.

@Bennet it hasn't. This entire thread (You need to read all it, not just the last two pages), until you managed to get an answer from the OP, has been based on supposition and obscurity on the purpose and ultimately reasoning behind the question, whilst altering the question subtly when not...

At last. An actual description of the mythical Unicorn project. Absolute worst case you'll possibly need 2 or 3 different front ends, connected to a single proper DBMS. Only taken the thick end of 100 posts for you to actually write something that made sense.

Add another column to your form or put a combo in the header (Which is purely for data entry not stored) which is Product type. Filter the Product combo to only those items - you can get funky with it and only apply it when the combo gets focus on the detail line, so it doesn't affect the other...