Cannot write to a read-only file foxpro

Can that user create, close, open and modify a textfile at the same location as your dbfs? Visual FoxPro: It's magic! Not sure what you mean by a different network share, could you elaborate? It is on a network share, but I'm not sure what you mean by different. I will check on the modifying a text file as soon as I can get someone over there to try it.

I know what you are talking about with the select into cursor, but that's not happening here, the actual command to open the DBF is It must be a permissions problem, but all permissions appear to be correctly set. There is a readonly attribute on the folder that cannot be removed through windows. Supposedly it can be removed through a command prompt with the attrib command, but I tried that and it didn't work. A Microsoft knowledge base article mentions this, and says that it can sometimes prevent certain programs from writing to that folder, so perhaps that is part of the problem.

If you're interested, it is KB The same thing happens with a text file in that directory, the user cannot save it because it's read only, so it doesn't appear to be a Fox specific issue. I have the network administrator working on it, but we're both kind of stumped.

Am I right? Note, to David's point, you may be "Pointing" to a Foxuser. DBF on the server, in which case, it may also be the problem. Also, can you send the bit of code that is the "Offending" lines? Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework. The Tek-Tips staff will check this out and take appropriate action. Click Here to join Tek-Tips and talk with other members! Already a Member? Join your peers on the Internet's largest technical computer professional community.

It's easy to join and it's free. Register now while it's still free! Already a member? Close this window and log in. Join Us Close. Join Tek-Tips Forums! No Address Book database found No document in that direction No document is selected; please select a document to respond to. Use 'Forward' on the 'Actions' menu instead. Warning: if you choose Yes, the database and all of its documents will be deleted. Please place cursor at the desired insertion point of the body field Query is not understandable Remote path name must be relative to Data Directory Remote system no longer responding Remote system not responding Remove selected item s?

Remove anyway? Replacing a database design changes the database's views except private ones , forms, agents, and fields to match those in the template. Do you wish to proceed? Replication of this database is not permitted Selected font does not have a consistent face, size, style, or color Server Error: Insufficient Memory Server Error: The signature on the certificate was found to be invalid.

Check the log file for details. Some preferences will not take effect until next time the program is started Sorry, an application to open this document cannot be found Sorry, you must have Designer access to be able to create or delete a full-text index The access control list is full.

If you need to add new users, place existing users into groups on the list. The certificate s have not been issued to you and cannot be merged into your ID file. The database cannot be read due to an invalid on disk structure The Doclink database cannot be located The executable program library cannot be found The first categorized column in this view does not sort on the Categories field.

Choose another categorized view using the View menu. The ID file is a safe copy and cannot be used for that purpose The ID file is locked by another process. Try again later. The linked document cannot be found in the view The maximum space for display of views, forms, agents, and shared fields has been exceeded for this database. So an insulation layer is a good architectural idea that comes at the cost of slightly deeper hierarchies. Now, if you're following along, you see that we soon have all these classes in all these layers!

How best to deal with them? A class library is a physical package of classes. But classes can -- and should -- be abstracted in a variety of other ways. The Component Gallery is great for creating virtual and abstract groupings of related items in a way that personally suits a particular situation. Good Practice: Use Ken Levy's superclass tool; it lets you see exactly what your inheriting. The deeper your class hierarchies, the more you'll appreciate tools like SuperCls.

Supercls gives you the ability to see and edit superclass code while working in the class designer's code editing windows. To switch project mappings all you have to do is double click the file in explorer. Visual SourceSafe only lets one person check out a class library at the same time. Individual classes, be they stored in VCX or. PRG files, cannot be individually checked out. So checking out a class means checking out the library wherein the class lives.

Moreover the probability of finding that a particular library is not available for immediate exclusive use rises with the intensity of development, the number of concurrent developers, and with the number of classes in each library.

These forces imply that you should, as much as possible, shoot for small class libraries. It's a good idea to use class libraries to package things that should be packaged together. If this is so, then checking out a class library should give you exclusive access to things that are functionally related. So when designing class libraries, think cohesion instead of type. In this sense, unless you work alone or in a very small team, having a class library for "buttons" or "forms" makes little sense.

At first glance segmenting classes into libraries appears simple: Keep first-level subclasses in one VCXes, all forms together in one VCX, cool controls together in another, with other VCXes for, say, composite classes, forms, toolbars, and so on. Everything is straightforward and, if anything, things are easy to find.

But the guiding principle of class library segmentation is coupling. Physically arrange your classes so that distributing and reusing them is not hampered by external dependencies. Classes that depend on each other should probably be stored together, or proximately in related class libraries.