Search results

If you mean controlling the UK PC from abroad then, yes, great minds think alike (!) but the user didn't like that solution (*) when we suggested it to him and he's the one in charge so we had to keep looking. * His issue was that he wouldn't be able to remotely use the UK PC while his...

We have a desktop Access 2007 app that's split into front-end / back-end components. As well as updating the back-end data, the app creates Excel & PDF documents in a number of sub-folders which exist in the same folder as the back-end. It's quite a complicated data structure and the app has...

Just checked namliam's point - he's quite right. That's what I get for answering off the top of my head rather than testing my theories ;)

Something like select <whatever> from <table> where year(nz(Field1,'1 Jan 1899')) = pYear or year(nz(Field2,'1 Jan 1899')) = pYear or year(nz(Field3,'1 Jan 1899')) = pYear or year(nz(Field4,'1 Jan 1899')) = pYear where pYear is the year for which you want data and it won't be 1899!

You need an IN condition in your parameter query e.g. Select <fields> from <table> where [Pricing Type] IN pRequiredTypes then set up pRequiredTypes containing either (1), (2) or (1,2)

All the validation should appear in the Click event for the Save button rather than in the events behind the bound controls. Do that and life will become much simpler.

There shouldn't be a standard close option any longer (step 1 in my original post) or do you mean your custom SAVE button? if so, what code do you have behind that? And are you auto-populating any fields when the form loads?

1. In Form properties, set 'Close button' to false 2. Add a CANCEL button with code something like this behind it: If Me.Dirty Then DoCmd.DoMenuItem acFormBar, acEditMenu, acUndo, , acMenuVer70 End if DoCmd.Close

Re. the back-up routine, I'd be amazed if that's causing the issue. Your PC spec sounds fine. I thought you might have had something state-of-the-ark rather than state-of-the-art. I'm stumped, I'm afraid. Is there any chance of splitting it into separate front-ends, one that deals with the...

When you say you've moved to Access 2010, have you actually tried going from .mdb to .accdb? Sadly, I think I can guess what your answer's going to be :( Alternatively, Is your PC fairly high spec? If not, can you try it on something meatier? (Yes, I'm clutching at straws!)

Add a MsgBox to the OnClick code to display the value of Me.txtOrder. At least that should tell you whether you're even trying to pass the required value to frmOrders

What you're suggesting doesn't surprise me I but don't think you can put a maximum on the number of elements before you start getting problems. It will probably also depend on the size / complexity of some of these elements especially forms. Has the front-end been compacted recently? If not...

... or should your code be DoCmd.OpenForm "frmOrders", acNormal, , "OrderID=" & myOrder, acFormEdit, , "Edit" ... so that it uses the integer variable you populated from Me.txtOrder? By the way, do you have Option Explicit set in your code module?

If an import hits errors it creates an ImportErrors table - can't remember the exact name format, I think it contains the name of the table being imported to. If you were to delete-if-present that table prior to the import then check again for its presence afterwards you'd know whether the...

Surely you could drop the Excel processing and instead get the files straight into Access then do the cleansing & reformatting there. Sounds worryingly similar to a process which I'm currently optimising for a client. At the moment the data arrives in Excel format, goes through an Excel app...

In the report's Data properties tab, the Record Source isn't quite correct. You've used an INNER join between the Soldier table and the Children table which means that only Soldiers who have at least one child will appear on the report. You need to change it to a LEFT join which will include all...

You could have the back-end on a web-based MySQL database with the front-end developed in Access. That would cut the learning curve.

So on January 26th I might be paying for December, January and February and it would appear as three separate records with the same payment date. I think the first issue you have to address is whether the totals are supposed to be by payment date or effective month / year. If it's payment date...

One way of doing it is to turn every = into a BETWEEN then use a NZ construct for each of the comparison values e.g. change tbl1.f1 = frm1.textBox1 into tbl1.f1 between nz(frm1.textBox1,0) and nz(frm1.textBox1,999999) If it's a date field use 1 jan 1900 and 31 dec 2999 as the NZ...

Wouldn't it be easier to check / process the files one at a time, in a loop?