Search results

That's usually the way to solve a problem! Drop me a line if you want a second opinion Regards Guy SE London

Thanks again for all you help I have posted similar remarks to this thread on the MS Access User Voice forum and they have already responded Will revert on the benefits I found from using large number with examples Regards

Thanks for the feedback Ridders / ArnelGP I tried ArnelGP's vba replacement for DMax and DMin, worked a treat, has saved me a day coding and testing. Fantastic Still, would be good to hear from Microsoft as to why DMax,min no longer work and if they perceive this as a bug Cheers Guy

Thanks for the reply, confirms what I thought I need the large number data type, I am working with numbers requiring 58 bytes storage (and beyond) as part of a research project. I have used Allen Browne's elookup construct to replace DLookup as was hitting "too many databases", almost cured...

Thanks for the quick reply As per my initial post, I protected against the Null (as per your suggestion) by using the NZ construct, I always do this The problem is that DMAX always returns Null, IE DMax fails when the Field Type is "large number". I could use a recordset and order by size...

I have been using DMAX,DMIN,DCOUNT,DSUM successfully with VBA for some time (Access 365). I noted the introduction of the LARGE NUMBER data type and have had cause to use it. Surprised to note that DMAX doesn't work, IE returns Null I protected against the Null using NZ but I need to find...

Hi, I opened your sample database and was able to inspect your VBA, couldn't locate any DMAX constructs. Did you solve your problem, if not I am sure I can assist

Hi I have been programming seriously in VBA since 2013, SQL for much longer Before VBA I used mainly C Although I am not an expert in VBA or SQL by any means I use them every day and am towards the end of a large office automation project based on access / SQL / VBA / HTML. Based in SE...