Subject Re: Getting a strange rowset is read-only message From Dennis <dphoover@comcast.net> Date Sat, 19 Aug 2023 13:38:24 -0400 Newsgroups dbase.getting-started Attachment(s) BDE.jpg See attached. Don't see any local share option. Dennis Wrote: > Thanks so much Akshat. I will look for the local share option but I didn\'t really see that option using DBASE driver. It looks like your example may be using an ODBC driver with more options. > > Unfortunately, I have no access to author computer, any source code, etc. its all been notes I\'ve written as I learn more about the code and DB tables. Super tough. > > I just don\'t know why the exact same config on Windows 7 had no issues but on Windows 10 I am getting this rowset is read-only when I add the second computer. > > thanks again. > > > > > > > Akshat Kapoor Wrote: > > > Good Afternoon Dennis, > > > > > I have two new Windows 10 computers running a Dbase 2.8 application. > > > The application worked fine with two Windows 7 computers but I am now getting a message on one that the rowset is read-only when I go to specific areas of the application. > > > I have checked permissions and tried multiple configurations of local files but I can\'t figure out what is different with Windows 10 shared database/application files. > > > What am I missing? > > > > Have a look at the attached screenshot. The localshare setting should be > > true. > > > > This is essential for sharing. But apart from that without any code I > > doubt anyone will be able to help you out. > > > > If I have a look at code that I wrote some time ago it takes time to > > understand it. Maintaining a legacy system that too without code. You > > deserve credit. > > > > There are multiple reasons for a rowset to be read only. One of them > > could be that some upgrade (which the original owner had not applied) > > fixed something and that is causing an error. > > Or may be windows changed something. Damn difficult to say. > > > > By any chance do you have any access to original author\'s computer. The > > source code files may be hidden somewhere. > > > > Regards > > Akshat >