Recent content by GPGeorge

This this in the click event of your command button. Private Sub CmdSalir_Click() On Error Resume Next 'DoCmd.Close DoCmd.Close Objecttype:=acForm, ObjectName:=Me.Name, Save:=acSaveNo End Sub

Pat. Can I get a copy of an accdb BE that has hidden Access indexes so I can see what the current version of SSMA does with it? If so, can you call out the specific indexes so I can focus on them? I've looked over the reports; they seem pretty thorough, but I could be missing something.

"ROWVERSION is deprecated and TIMESTAMP is its replacement, I think since v2005." Can you provide the link documenting that Rowversion is the one deprecated? It's counter to everything I've read on the topic. For example...

That is a direct quote from the Microsoft document itself. The one I linked to in my post. It literally says "the SYNTAX is deprecated" and will be removed in a future version of SQL Server. I went on to add that it's ambiguous, which this discussion seems to confirm. It is very confusing, as...

The term "TimeStamp" is supposed to be deprecated in favor of "RowVersion", but the function itself remains. The Learn article on Rowversion does appear to be ambiguous, though. The timestamp syntax is deprecated. This feature will be removed in a future version of SQL Server. Avoid using this...

One more reason to eschew macros and employ VBA.

What does that mean? You can't link PDF's directly from folders? Access developers do that all the time! All you need is a field in the table containing the path to the PDF....

Microsoft did make such a move a couple of decades ago. It never succeeded and DAO regained prominence. It's no longer an argument for ADO itself. There are other advantages to ADO, though, for situations where it makes sense, such as disconnected recordsets.

You didn't mention the elephant in the room for attachments: file bloat. Regardless of how well or how poorly the attachment field itself performs, inserting binary files (Word docs, PDFs, Excel sheets, images, etc.) inside the accdb doesn't make sense. Fight me to prove me wrong.

Experience is a good teacher. ;)

The_Doc_Man has addressed the underlying problem as well as the other key problem of splitting data into multiple accdbs. Storing binary files, i.e. PDFs, Word Docs, images, etc. inside an accdb is possible, but highly undesirable. And even more so with the large volume of information you need...

SSMA has been enhanced quite a bit in recent versions. Pre-migration reports, for example, are very informative about what will be moved and how, but more importantly most of the potential problems are flagged for your attention. Check out this video from last fall.

Given the uncommon approach here, it's hard to see how this can be a successful design. But assuming for a moment that you will eventually sort out the various problems it introduces, let's focus on what this statement means. "... insert employees1.*, employees2.*, employees3.* the results all...

Are you sure the full SQL is not there? Have you expanded the row height of those fields to inspect the entire contents of the field?

I settled on the tempvars alternative with the use of the criteria I explained above for two reasons. The VBA is about as simple as it gets. Two lines are needed. One to set the tempvars value One to requery the form. That's it. There is no need to swap or modify the row source or...