>>Views doesn't need exclusive access but would be good of course.
>>Open database ...
>>Drop view ...
>>Create SQL view as ...
>>works on the fly.
>
>Hey Cetin,
>
>What if I normally do everything through the project manager and I don't have access to the client side except to send them files? or go there? ...which is what I'm really trying to avoid... Is Trey's solution the most viable?
>
>Renoir

Renoir,
I never said go to client side (I have clients in US but never been abroad yet). Those were skeleton lines for update code to send client.
Forget about Exclusivity part since I wouldn't dare to do it myself. A table or view or the whole DBC could be created, recreated in code using many commands like :
alter table...
add table...
free table...
drop view...
create SQL View...etc, right ?
To get programmatic version or your DBC use home()+'tools\gendbc\gendbc'. You would need to play with it in order not to destroy existing data. However you said views. Views are only definitions, not physical tables so probably all you need would be 'create SQL view ...' 'dbsetprop(..)' parts + an addition to drop them first. If you fail to include a field used in current forms than it's like providing a new table with missing field.
I haven't yet read Trey's suggestion but I'm sure it's a good one and much detailed than my original reply.
Cetin