Recent content by InstructionWhich7142

It's SQL Anywhere not Sybase, sorry. I have tried closing and re-opening and adding new links etc. To be sure it wasn't some kind of "these were linked before" error I created a new blank database, manually enabled that setting, saved and closed then re-opened and created fresh links, still got...

Yep, it prompted me when I first tried to connect to either basically enable that or stay in old compatibility mode, I enabled it, I've just closed and re-opened the database and it's still ticked in "current database"

Hi, With the latest SQL Anywhere 17 64-bit drivers direct from SAPs website and 64-bit MS Access freshly installed from Office365 website on Windows Server 2022 I get #Deleted instead of data for some tables - seemingly ones using an ID/PK field of the BigInt type - loading these as Snapshot...

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