Mel:

>Well, that was the problem. I for sure had the correct property set in the cWorkArea, but it was in all Lower case such as workareaname instead of Workareaname. I realized from early on that when you have a field or table/view name in a method that it was case sensitive. But, I just didn't realize it was that sensitive when assigning values in the Properties window.

Huh? Codemine isn't case sensitive, nor is the properties window either. I'm not sure what you have done here <s> ? What you may be getting confused with is that the general Codemine convention when testing for entity names like a cursor or column name is that the framework pushes the entity name through the Proper function. So, irrespective of whether you have "workareaname" or "Workareaname" in the property sheet, in the relevent method, when you test for something, you have to ensure that what you are testing against the method's cWorkarea parameter has been "proper'ized" by you <s>. Otherwise, you are comparing two strings that may have different case and therefore your testing code may fail. But just to re-iterate, Codemine is not case-sensitive. On this basis, if you are unsure whether a cWorkarea is coming in to the method in proper case, at the start the method, you could always do something like :-

lparameters cWorkarea
m.cWorkarea = Proper(m.cWorkarea)   && Assume that a value "MyTable" is coming in.
*-- If Codemine for some reason didn't set this to proper case which it usually does, it is now!
if m.cWorkarea == 'Mytable'   && This constant has been typed in proper case.
   *-- Both values are propercase and therefore, this test will work.
endif

Just ensure that any value you compare against m.cWorkarea has proper case. Are you with that?

>Yes I did change this from a table to a view. For clarification are you saying I need to uncheck the exclusive when I move from a table to a view

No, what I am saying is that you dont want the exclusive flag set at all, even if it is a table, unless you really want exlusive access to the table which will very effectively deny access to the table to other users on your LAN. Generally, exclusive opening of a table is only utilised to do maintenance processes on the table viz., packing, modifying, reindexing etc. If you dont want other users to access the table when you are using it, then open it shared (the default) and use FLOCK() to lock it.

>as CDE will always check the Exclusive?

Again, I'm not sure that it does always do this - mine doesn't ? Most table use in a system is non-exclusive otherwise other users could not access shared data in the table. It may be that in your Visual Foxpro preferences, you have the default set to open tables in exclusive mode and therefore the Codemine builder may be defaulting to this setting. In VFP, look in Tools, Options, Data and see what you have in your "Open Exclusive" check box. It really should be empty.

>Again, thanks a million. You have been a tremendous help as always.

OK, OK, just give me my stars and we will say no more about it <bg>

Best