Search results for query: *

Select @variable= Coding + ',' + Testing + ',' + @Integration from Table1 where ... Insert into Table2 Values (@variable) ?

sp_helptext config might have done it.

I've also had VCXs behave slightly odd sometimes - eg a single class stop working. But I too have never got to the bottom of it - I just rely on having source code version control to make sure I don't lose too much.

Fascinating. I tried doing a grid with the first column disabled, and guess what - column2 got focus before the column I clicked on. Raise it as a bug with MS? I suppose that leaves the option of putting a "hasTheGridBeenSelected" flag on your form, so that the code that fills grid doesn't...

I suspect that an 'optimum' solution (whatever I mean by that) is several thousand files per folder because: It used to be the case on Dos/Fat that you'd get a noticeable slowdown after a couple of hundred files. In other words, even on FAT you're okay with 100 files per folder. NTFS wiped...

Your code doesn't look kludgier that the normal standard of T-SQL to me ... Since the code you give doesn't actually create a stored procedure, (i.e. it's not of the form: Create Procedure procName( @newsletter int) As) could you assure us that (1) you have created an sp to run this code and...

Chris, Where did you get the "winmgmts:" name from? Thanks, Chris

Do the following: Create Project MyApp Then, add your forms to the project. Then, create a program file called MyAppMain.prg containing this: Do Form MyForm1 Read Events (Obviously replace the name of the Form with the correct name). Then, right click on the icon for MyAppMain.prg in your...

I don't know - but I suppose as an option you could change your update job to run every 4 minutes or every 6 minutes instead of 5 minutes, and then you can time it to not overlap with the merge replication (assuming each process takes less than 2 minutes to complete)

I would guess that the reason your trigger is inserting rows into the subtable is because you have the line insert into tbl_policies_sub_donna .... So you've told it to insert. Your mistake seems to be to declare your trigger for update and delete as well as insert. Why not declare it as...

Is there a reason for trying to to this with a trigger rather than a calculated column? It does seem to me that a calculated column is designed to to exactly what you want without the hassle of a trigger. What you really want is Drop Trigger trgConcat Alter Table temp_table Drop Column...

It's a Windows Explorer feature, not the QA. I had the same thing in several programs until I realised that the Explorer options were affecting open/save dialogs! Chris

If you know for a fact that the owner names are different then that is likely the cause of the problem and I don't think there is a way to write one view that works on both servers. Sql Server always names its tables as ownername.tablename. A typical VFP view, 'behind the scenes' is defined as...

Yo ho, In proposing a container, I'm not proposing to make a class of it. I acknowledge that what I say represents a 'new' use of container. But: the desire for (and ability to properly do) flexible layout is also new. Hence a new solution (well, okay, a solution nicked from Java). I submit that...

Better late than never: Changing ports made no difference to my problem with ZoneAlarm

Noooo, there's nothing wrong with an extra layer of container! It's a mindset thing. In Fox, we haven't really done (well I haven't really done) flexible/moving layout before. In Java and coming up now in .Net, flexible layout is the norm. And it's done by nesting containers. It makes sense...

SCATTER hasn't changed at all. The migration issue from 2.6 to VFP is: In 2.6, variables declared or scattered private in a Form's init become declared at the top of the generated .SPR file. The rest of the form is coded inside that same .SPR file and hence the variables are all in scope. With...

Try this: Put the three buttons inside a container. Put container.anchor=260 Make the container transparent and edgeless. I got 260 by looking at what the builder offered for anchor values for a single button. 260 was 'centred at bottom of form' with no resizing.

Well, it's worth making some effort to get code to work. Cheers, Chris

(aside: The 'Can't edit' message in MS SQL is because from SQL Servers's point of view it the column doesn't correspond to any data in the database. This has no bearing on the Foxpro situation, where FoxPro has created a cursor in which nChoice is now editable data.) I have just created a form...