Search results

Alternatively (assuming you've built the new table in your front end) simply use DoCmd.TransferDatabase with TransferType:=acExport ObjectType:=acTable etc .... to move it the BE and the DoCmd.TransferDatabase TransferType:=acLink ObjectType:=acTable etc .... to link to it.

Agreed to both but MSysObject never updates unbound forms and reports .DateUpdate, whereas CurrentProject .DateModified is good enough for sorting.

The trouble with using MSysObjects is that DateUpdate field is not as accurate or up to date as the CurrentProject.Allobjects(objectname).DateModified which I use for various purposes.

See what you mean - of course information about the 32 Bit API isn't easily available anymore, unless. like me, you still have a copy of Visual Basic programmer's Guide to the Win32 API by Dan Appleman. ISBN 978 0672315909. Given me the idea for a new thread on using books rather than just...

Don't worry about it being 32 bit code: it still works. And given how just how much 32 bit code is still used by the Access 64 bit application it will be for some time yet! Usual warnings about need to use PtrSafe in declarations, of course.

You can achieve much the same by: In the 'good old days' with Access 2003 an Visual SourceSafe when this happened I just recreated the database from VSS. If you are using Access-vcs you can do the equivalent (assuming you have kept your repository up to date).

I've read the thread with great interest and generally all the advice is good. However, I would point out the steps you need, all desribed in one way or another above are: There must be fully described specification of what the changes are supposed to do (an what the must not do)! There must...

Learned something in this thread! I have always use Application.CurrentProject for the All(Object) collections and bodged it with iterating querydefs for queries . Now I can swap swap to using Application.Currentdata for queries. Proves that no matter how much you think you know there's...

A word of warning about gun control. In the UK we have the strictest gun control laws anywhere probably. The normal citizen may not own a gun full stop (period in US speak) - there are exceptions where required for work etc such as farmers and gamekeepers, but they are few and far between...

To contact an Administrator go to the main forum page and Right Click on any of the Staff Online and start a conversation. I had the same problem as you and it tuned out it was because I was trying to post with an embedded link and I've made fewer than a 100 posts. It's an anti-spam measure...

If that's what he meant then you are right - however, what he said was duplicate records and that is exactly what DISTINCT ROW does. Mind you as I said in my first post "Have I missed something ' and I obviously had.

The initial post says duplicate records and this is what DISTINCT ROW does. A record is a row: if they are duplicates only one will be seen.

Have I missed something but is there any reason why nobody has suggested using the DISTINCT / DISTINCT ROW predicate? As a aside, which may not be of much use in this particular case, remember that no duplicate records are returned when you use a UNION operation, unless you specify ALL.

You are absolutely correct - my accounts database which has at least one attachment for most transaction has 1181 attached files running to 276 MB - imagine them embedded in the database!. Not to mention the 1,630 attachments of cover photos in my Library database.

Does anyone else find the limitations of the Attachment data type frustrating. I tried it at some length when forced to move from Access 2003 and Win 8.1 to Access 2021 on Win 10, but it just didn't do what I used to do with a set of forms and routines I developed on 2003. I have reverted to...

I too am using msaccess-vcs and WinMerge and other tools, especially the command line version of WinZip to tuck away (and when necessary, retrieve from) each release. However, it doesn't alter the fact that VSS did all of these things in one simple integrated tool, and I miss its simplicity.

Interesting - I couldn't put that link into the forum! It's where I got it from.

I found it by typing OIS.EXE into Google.

The one thing I will say about this ongoing discussion about source code management is that I find it truly frustrating that, having been forced to finally move from Office 2003 by hardware failure, they are now my problems. Previously all these feature were available via the Visual SourceSafe...

A number of thoughts on putting forms in Library Databases, a bit randomly presented; Generally: First of all - if it works for you great, but you won't find me doing it. Secondly remember Forms are classes. Indeed in Access 95 for members with long enough memories we used hidden forms as...