Search results

I would disagree depending on how you are actually storing the ancillary order information. If you are creating multiple line item invoices, I personally wouldn't want to store the PO, Contact Details, Order delivery instructions et al. on every line? That seems very wasteful on storage (which...

Welcome to AWF. Two things - is this a class assignment? And show us your table structure, because if it's laid out as above you have much more serious problems with the way your data is stored.

Wow, that's a really serious wildfire. I hope nature can contain it or put it out as I doubt us poor little humans can.

You have to store the VAT per line, as the line items might have different vat rates. No choice. For a suppliers invoice I would record the VAT they charged per line regardless of the calculation. Using one form for both would be problematical, but not impossible. I'm not sure I would go down...

You need to check the record count in the subform first, something like If Me.frmOrderAddEquip.Form.Recordset.RecordCount = 0 Then ...

But, if it was simply ticked by default in new databases, it wouldn't cause a problem in existing ones? And noobies would get an obvious error in their code?

We had no issues with Amazon returns, and we use them a lot, but always price check, and check the supplier direct if possible. UK based, and Amazon are very helpful normally.

Have you tried removing any internal margin settings: I have seen some odd effects, particularly on combo boxes, when these are anything other than 0 and coloured backgrounds are used. They might be exacerbated by the scaling in the environment.

You have a typo in your function Interal = "m" But suspect that might be an editing issue rather than you source of your problem. When you remove the criteria, sort your results on the calculated expiry date (ascending and then decsending , and see what you get. If you can't spot the error...

That will restrict you to exactly 6 characters. If it's an unbound form then in the "Change Password" command button use something like If Len(Me.MyNewPasswordControl) < 6 Then msgbox "The new password supplied is not long enough",vbInformation,"Check Password"...

I suspect it's links, even to other posts. You can't post links until you have a 100 posts to prevent spammers / advertising.

I wouldn't mess with that - it's used as a temporary store for the data whilst Access is doing the compact and repair. It sounds as if you have it set to compact on close, which isn't generally considered good practice?

The DATABASE.mdb file is normally created when a compact and repair is run on close.

Try displaying a report in a form, that would possibly work as you can change the font per detail line in the format event?

@emmanuelkatto , @emmanuelkatto23 , @emmanuelkatto24 You are going on my ignore list as you have failed to respond to any of the answers provided in any of your myriad questions. This tends to make me think you are either a bot, or a wind up, or simply here to waste peoples time.

I can see a sensible pattern to work with but what I can't see is the source data. In these circumstances it is often better to have two samples - The data you have to start with and the secondly the desired output. So ideally we need two excel sheets - starting data, and expected final output...

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...