 Prasanna asks us, I want to extract data from WSS old version. What is it? Do you don't need to modify WSS with old version? Yeah, they're worse. The old version. Superness, yeah. To SharePoint 2016, which by the way, Prasanna, is an old version. But the data stored in SQL as tables is in that my table, in that my table, my list is an item, is as item. I'm going to read that over again. So we'll just take the credit and get a list out. In SQL as tables, in that table, my list is as item, how to retrieve the list from WSS. So I can speak to that. So let's first establish what WSS old version is, because if you're going technically, there was WSS, Windows SharePoint Services Version 2, which was back in the 2003 days. WSS Version 3, which was 2007. And then it turned over to SharePoint, what was it? I want to say framework, but not framework. Foundation. Wasn't it just some SharePoint Foundation? Foundation, thank you. And who was an F? It's always F. You were getting there. You were getting there. So in any case, the thing is around SharePoint 2010, which is going to be when SharePoint framework, excuse me, SharePoint Foundation, yeah, actually came along. Thank you for my translators here. Microsoft added something called unattached database recovery, but it does not go back prior to 2010. But that would allow you to attach content database into a SharePoint farm and run export operations against it to get lists and content out. If you're going back to WSS v2 or v3, what you're literally going to end up going against the database, and there's no wonderful answer there. So I wish I had paid a little more attention to the WSS old version part of this. The minute I saw WSS, I'm like, I'm not putting an X next to that. I'm not even having a conversation about this. We're not even going there. The truth of the matter is, though, I mean, there are a few really super clunky ways to do it. Probably you could go directly to the table and PowerShell and export it out and put it into something like a CSV file and then pull it back in. You could copy and paste it. And there's some really clunky ways to do this. There's just no nice ways. Yeah, well, in all likelihood, I mean, the biggest challenge I think is going to be finding a tool still out there because there are plenty of ways to your point, Sharon, people did this. But PowerShell wasn't one of them because PowerShell wasn't around then. PowerShell actually was usable in the 2007 days, but only if you were using the .NET framework. There was no PowerShell command let set for SharePoint at that point. Yeah. So I know guys like Keith Ritchie back when he was doing more extensive work in the old versions, he would put out different things. And you probably have to look for him online. But if you can find somebody old enough still doing SharePoint and you want to buy him a beer, I'll bet you can probably get a decent approach to addressing this question. Unlike this group of young kids like we're not going to know. So yeah. My only thought on that, because I used to attach to my database, access databases to SharePoint tables. That's another way to pull it out too. If they, when you've got connected or looked up lists, I don't know the complexity of her table or whatever it is, because you can't kind of read what's in there. And the question is a little bit garbled. But yeah, SharePoint or access might be an option too, because you can import the list of the SharePoint. Access is always a nice clunky workaround. It's kind of funny like it kind of does the job sometimes, but it is definitely, sometimes it's more work than it's worth. I did it. I used it today to go in. It won't let me set a unique value on a column and saying there's something in here. So I think there's 5000 plus items in there. So I went in and I said, I need to find duplicates query and it showed me all the ones that were used. Very nice, very nice. Access forever. Yay. Access for the win. Yay. Yeah. That's like the worst time I think I'll say that ever. Access is a nightmare to me. It's my friend. Yeah, I might do back and out. Find unmatched queries all day long every day. I wish I could do those in SharePoint. Back in the days when I was a disaster recovery architect and I was trying to discover all of the mission critical applications in the company I was working for, I cannot tell you the number of access databases running on people's PCs at their desk that were mission critical, not on IT's radar, not backed up. And they were all access 2.0. And that's how I made my living. Don't knock it. I think access database is into other things. Yeah, there's also an ulcer and a heart attack in that, Sherry. I literally have an open project. I really swear to God, have an open project right now. I'm moving two access databases from somebody's desk into SharePoint as a solution for now. It'll go into Power Apps and it will ultimately end up becoming a custom solution. But it's kind of in it's our little transition phase. Still working on him. That's great. Now paste a pen query to update the data. John, I don't believe that you read the small print when you signed up to do these that we are an access friendly group here. I know. I'm not a hater. Use the right tool. Yeah. Yeah. Which is never access. Oh, I'm sorry. I said it again, didn't I? Booth. Excuse me.