Welcome To The Home Of The Visual FoxPro Experts  
home. signup. forum. archives. search. google. articles. downloads. faq. members. weblogs. file info. rss.
 From: Paul Walters
  Where is Paul Walters?
 Gladstone
 Michigan - United States
 Paul Walters
 To: Andy Kramek
  Where is Andy Kramek?
 Hot Springs Village
 Arkansas - United States
 Andy Kramek
 Tags
Subject: RE: pesky read only problem
Thread ID: 78809 Message ID: 78860 # Views: 1 # Ratings: 0
Version: Visual FoxPro 9 Category: Distribution and InstallShield
Date: Sunday, October 09, 2005 11:44:13 PM         
   


Thanks to both, Andy and Andy

I can't believe I did not catch that. I quess it has been too long since I compiled an executable. I actually remember wondering why the DBC was excluded in the old APP.


> > I have been receiving error 111 - "Cannot update cursor" when running either a compiled application or executable. This includes applications written 8 years ago that worked until I have recently opened them. I am using VFP 5.0. Here is an example of the problem and what I have tried.
>
> Sounds like you have included the tables and the DBC in the project. In this case they will be read-only when you compile it into an EXE but will work perfectly well when NOT running as an EXE. To check, do the following:
>
> [1] Open your project
> [2] Go to the DATA tab and expand the "Databases" node
> [3] Look at the database and you should see a little "No-Entry" (circle with a bar through it) icon next to the name. If not, then this is your problem - you are "including" the DBC in the build, thereby making it read-only at run time.
> [4] To correct this, right-click on the database name and choose "Exclude" from the shortcut menu. You should now see the little icon appear.
>
> Repeat Steps [3] and [4] for each table making sure that all tables are excluded from the build
>
> Re-compile your application and all should now work as expected.
>
>
> Regards
> Andy Kramek
> Microsoft MVP (Visual FoxPro)
> Tightline Computers Inc, Akron Ohio, USA


ENTIRE THREAD

pesky read only problem Posted by peter gee @ 10/9/2005 4:08:24 AM
RE: pesky read only problem Posted by Andy Kramek @ 10/9/2005 2:20:39 PM
RE: pesky read only problem Posted by Paul Walters @ 10/9/2005 4:29:04 PM
RE: pesky read only problem Posted by Andy Beebe @ 10/9/2005 6:38:59 PM
RE: pesky read only problem Posted by Andy Kramek @ 10/9/2005 9:13:54 PM
RE: pesky read only problem Posted by Paul Walters @ 10/9/2005 11:44:13 PM
RE: pesky read only problem Posted by peter gee @ 10/10/2005 2:17:29 PM
RE: pesky read only problem Posted by John Peart @ 10/10/2005 3:05:06 PM
RE: pesky read only problem Posted by peter gee @ 10/10/2005 10:59:44 PM