Fixing columns in a grid

[Jerim65]

I am very keen to 'fix' the first three columns of a grid which will always display 4 columns - Y,M,D,and a Memo field.

I have found thread184-1255205 but I am unsure how to get it to work.

My grid is created programmaticly from a form.

In the methods I have things like Procedure BtnExit.click() which is run by clicking the BtnExit objectI have added and programmed code for.

I have tried both Procedure Scrolled and Procedure AfterRowColChange but I don't know how to get them recognised in my grid.

Can anyone help please.

Ultimately I would like the first 3 columns to be fixed so If an edited version of the code for 2 columns given in the thread could be given I would appreciate that to.

Regards

Coldan

 

[Koen Piller]

Coldan,

Never mind it is not too late.
Believe me, if you are a capable programmer in doing it 'the programm way' (FoxPro 2.0 or dBaseIII) buy the book, find a mentor, and I am convinced within a week you are capable of making a working exe with 2 or 3 forms, a report and a grid with 3 locked columns. 50$ says you can!

Regards,

Jockey(2)

 

[Dan Freeman]

I'm not sure how I can force my head around 180 degrees to think in those terms - maybe it is too late in life. I know its supposedly never too late but my memory isn't what it used to be.

It's actually more like 45 degrees, and once you've made the effort you realize it's mostly in *packaging*.

Back in the FoxBase days, we all used a utility called FoxBind.exe to combine all of our PRG files into one for compiling. Just a different form of packaging the code.

Under the skin, VFP is still familiar old Xbase procedural code. But once you've adopted the new packaging you end up writing (and supporting, and debugging) a lot less of it so it's pretty useful packaging!

 

[Jerim65]

Hi Jockey(2)and Dan

Just to explain my circumstances further - my efforts in VFP concern 2 utility applications accessing 3rd party app's tables and ini files.

Both of my applications are 'complex' utilities written over the past 6 years with many reports and forms launched from a pageframe sequence - some containing grids with operation buttons within the forms - written in VP9 Sp2.
I 'automatically' compile to exe via [F2] programmed to run a batch file, with a manifest included to allow access to 'forbidden' areas that the users may have penetrated.
I use Inno compiler within the batch file and go to a newly installed exe in 'Program Files' in less than 60 secs.
My utilitys' setup files are (1)7Mb ( at Version 5)and (2)12 Mb (at Version 9) with only small tables included - others are written on the fly using 20+ 3rd party tables - so they are not trivial applications.

I respond to user requests for new features and dream some up overnight - thus my many requests for information to this forum as I attempt to implement these new features.

Thanks for helping!

Regards

Coldan

 

[Koen Piller]

Coldan,

would you believe I dont understand what you are trying to tell me? First you tell me you dont know anything about visual programming you do everything in prg files and now I read a story about an application in VFP92. Is everything written in procedures? Pageframes, grids, reports the lot?

The compilation into an exe wether you have an application written with procedures only or made the visual way is an other story. The (re)compilation of an application visualy built is done within a few seconds by just 1 click of a button.
The formate to an install project is only done once. When the exe is installed and a newer version with no changements to the database structure is a replacement of the old exe with the new, not Inno setup.


Regards,

Jockey(2)