Search results

From the description of the end goal, it appears there is a faulty table design here. It would not be proper design to have to store the same values from three different fields in a second table. I think I can guess what the tables actually look like based on this description, although this is...

Good point. I used that reference primarily to point out it's been around a long time, 30 years. I actually don't use it much, if at all, anymore because most of my personal databases have SQL Server back ends.

The J Street Relinker has served a lot of developers very well over many years. Here's the copyright notice for it in the version I use. Note the starting date. '-------------------------------------------------------------------- ' ' Copyright 1995-2009 J Street Technology, Inc. '...

And I assume that your IT has also designated the version of SSMS you currently use (19, 20, 21, 22?) as the default app to open .SQL files?

see Posts 41 and 42.

Re: cobol. Large financial institutions maintain applications written in COBOL because They work consistently and reliably, and have done so for decades. That's a Good Thing™ when you are managing billions of dollars of other people's money. The COBOL code base is enormous and deeply...

Thanks, Doc. That's the full explanation about why I made the observation I did, and why I highlighted the final phrase, "at that time". I was lazy and didn't bother to elaborate why that was so. I think a previous post in this thread regarding opening the "wrong" version of SSMS can be...

I find that doubling-clicking on a file with the .sql extension opens it in the program with which that extension is associated at that time.

I've been trying to recall an issue with Access back ends on network shares that was possibly associated with the 242H2 update. The only thing I come up with is that it had something to do with needing to disable leasing. Maybe someone will know what I'm talking about and can address whether...

Having migrated Access tables to SQL Server since the early 2000's, I've had the opportunity to do so in multiple ways. Who remembers when "Export to SQL Server" was an option on the Access ribbon and before that a Menu option? Each has advantages and disadvantages, and no that is not a waffle...

Unfortunately, the table in your current database is not yet suitable for a relational database application. It appears to be the result of importing an Excel worksheet into Access with no further effort to convert it into the appropriate tables. That is a very common mistake when first...

"... it makes it really easy to find ...." (y) I would add, "... and to make it clear what is happening." As I get further away from the halcyon days of head down programming for clients, I find it comforting to be able to read and follow the logic of fully qualified code structures.

You might also want to account for possible Nulls in CountryID WHERE (GrantsT.CountryID = 3 AND GrantsT.Status = "Active") OR (GrantsT.Status = "Completed" AND GrantsT.CountryID IS NOT NULL) That said, David's version is more likely to produce the correct result.

Thank you. I think this is another case where I adopted the practice of using full syntax regardless of whether it's required or not.

Please elaborate. In what context do you not need to use EXEC SP_MyAllPurposeSummary?

"Hey, Claude. Use the raw files in this GitHub Repo: https://github.com/GPGeorge/Context_LTFLibrary. The raw URLS are in the file called LTFCatalogRawURLs in that Repo. Discard any files you may have retrieved in earlier sessions. Use only these latest versions."

It's a public repository.

SSMS is tightly coupled to SQL Server in the sense that it is designed to work with SQL Server databases. However, it's important not to confuse the two. SQL Server -- the objects themselves, tables, views, stored procedures, etc. SSMS -- tools to create, modify or delete objects in the SQL...

What I do is export the files to GitHub and provide the AI (Claude in my case) the Raw URL's for those files. Claude needs to have access to the GitHub repo, so I created one just for that purpose. It also can't get to files in the repo directly, but it can retrieve them via the Raw URLs.

SQL Server Migration Assistant for Access (SSMA) is a tool that migrates tables from Access to SQL Server. SQL Server Management Studio (SSMS) does not enter into that migration process. You do not even have to have SSMS installed to migrate the tables to SQL Server. SSMS has NO objects of it's...