Search results

This is pretty close to the mark, the industry we're in has a long tail of spares and repairs orders so although stock is a few years old it's still likely to be used and sold at value or indeed at a marked up price based on current market availability and MOQs etc, after 5 years the likelihood...

(1-Round(xMin(xMax(((DateDiff("m",[everyday],Now())-60)/60),0),1),3)) perfection 👌

Datediff is a good point, I've used that elsewhere but it didn't occur to me here as I was modifying existing code that used format :-) You sound like our accountants lol 🤣 Yes we do keep the original value and this is just a written down value that's reported monthly so that simplifies...

So I used to do this by year but it was "bumpy" because if some high value thing suddenly loses 20% of it's value in one month of the year it looks higher than the other 12, it was suggested to do it by 1.66% per month instead, I ended up coming up with this abomination (i'd already written my...

I've amended for relevant versions, apologies for the spam and bad info, I just don't want to be DenverCoder9 if you know the XKCD and as I'd solved my issue I wanted to share back, cheers

Apologies, I know you an Doc would have got the notification a few times but it looked to be a subject everyone was revisiting so I thought for the benefit of the Original posters in each instance I'd share it on the 4 threads I'd delved into at least. It was only as I was looking for the name...

edit: apologies if I shouldn't have posted this 4 times but it's the answer to all 4 issues, at least in my case and I found I still had these threads open so thought I would share in-case the previous creators are still watching, delete if I'm in error, thanks I went through this thread and...

I went through this thread and some others, for reasons of ODBC compatibility with Foxpro i'm stuck on 32bit, and Access 2016/office365 has only recently been made Large Address Aware, so you may find your issues have resolved themselves, if you're still on 2010 it turns out this simple utility...

I went through this thread and some others, for reasons of ODBC compatibility with Foxpro i'm stuck on 32bit, and Access 2016/office365 has only recently been made Large Address Aware, so you may find your issues have resolved themselves, if you're still on 2010 it turns out this simple utility...

I went through this thread and some others, for reasons of ODBC compatibility with Foxpro i'm stuck on 32bit, and Access 2016/office365 has only recently been made Large Address Aware, so you may find your issues have resolved themselves, if you're still on 2010 it turns out this simple utility...

Having read into this a bit more I'm concerned the large 2 and 3 screen setups will cause issues with the TWIPS limits so I'm not sure I want to go the sticky forms route

Apologies, I gave up on that fragment by the look of it but didn't notice it was still hiding at the end there! Thanks for taking the time anyway. The Twips limit makes sense for the issues I'm seeing, but how does Access handle a 3 monitor setup that's wider than 22 inches? Is that why I'm...

Oh wow, I even thought that spelling may be it and read them carefully, I thought.......... clearly should have pasted them one above another! Embarrasing! I too am discovering this joy, for a long time (nearly 15 years! yikes!) I've used your fAccessWindow "HIDE" to hide the main window and...

Your centre form example is amazing, thanks! I'm currently using your ideas from it it to make a function called JustTheTop to vertically re-position a data sheet view form to be more sensibly in the middle of the screen, I did wonder though, how do you have popupForm3 and Popupform4 both...

Edit: fixed - Thanks! I do appreciate your help, by poking around trying to find the issue this time round it dawned on me to split the two separate Left Join routes with Table B & C in the original query and do Table A in the subsequent query, elegant enough, Just for speed etc I've ended up...

ah that may well be the issue, if the corresponding information isn't in that system then all the fields are effectively NULL, so the primary key (ID field) I'm joining on is also NULL, I don't see why you would use a LEFT join for anything else?

yes the data between the two tables can be in 3 or 4 states, I want to know the 3 where at least something doesn't match if that makes sense, something like A=B (I don't care) A not B B not A not B not A it's a query to identify records that lack corresponding information in another table...

I have the below , I tried NZ on every field but still get the error, removing the WHERE resolves it so you're spot on with that, I still don't really understand exactly why it doesn't like it? is it to do with how queries are almost processed "server side" and the results returned? and because...

The funny thing is there aren't any NULL values in any of the tables themselves, I've checked all the indexed columns. The only NULL is created when the SELECT query does RIGHT JOIN from tables with every item ID as a primary key, to a table with only some items Primary keys and other values...

I have a select query, it has 10 tables in, some are local, some are linked to FoxPro DBF via ODBC, some with inner joins, some with right, I'm expecting null values in some fields, however I get ODBC--call failed. [Microsoft][ODBC Visual FoxPro Driver]Index does not accept NULL. (#886) I had...