>> I want to create my own grid
WHY, just WHY?
Haven't yet found a problem for which I would need a homegrown grid.
What can't you do in VFP's native grid, in combination with the excellent
container hierarchy which you could add into any / every column of a grid?
Build a set of controls, save them as class, add that class to the Column,
change Column.CurrentControl to point to that class, set Column.Sparse to
.F. and presto, you can do any complicated setup and stil have the benefits
of VFP's native gridspeed.
wOOdy
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/019d01d4a5da$cfdfa0e0$6f9ee2a0$@wondzinski.de
** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
At 08:13 2019-01-06, <juergen@wondzinski.de> wrote:
> >> I want to create my own grid
>
>WHY, just WHY?
Because the VFP grid does not work.
>Haven't yet found a problem for which I would need a homegrown grid.
>What can't you do in VFP's native grid, in combination with the excellent
>container hierarchy which you could add into any / every column of a grid?
Full validation of a row.
I came close, but it required a lot of kludges and an innocent
change in one place could blow it up.
>Build a set of controls, save them as class, add that class to the Column,
>change Column.CurrentControl to point to that class, set Column.Sparse to
>.F. and presto, you can do any complicated setup and stil have the benefits
>of VFP's native gridspeed.
I wish.
One of the things that Grid is supposedly not for is data
entry. I need a grid that can handle that.
Sincerely,
Gene Wirchenko
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/d3e7c8e925ef9658f59e62571a4e9cb3@mtlp000084
** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
Hi Gene,
About this:
>"One of the things that Grid is supposedly not for is data
entry"
I don't agree. Not sure about the complexity of what you need to do, but if
you used FoxPro before VFP, you could remember that before the grid
component was the BROWSE command with many parameters that allowed many
validations and options for row/column, and that many validations and
options where made exactly for that purpose, for data entry. Most of them
have no sense for other purpose than data entry.
One of my first programming challenges was to do a component exactly as you
need it to (I'm talking about dBase III+ era), and could do it, but the
problem was that performed horribly, too slow to navigate records and
columns.
I think that you could face the same problem. Do not forget that you have
to control each and every aspect of the component, as:
- Scrolling left/right controlling start and end columns
- Scrolling top/bottom controlling start and end rows
- Controlling the data you load/unload, because you can't load a millon
records in memory, and this forces you to control dinamically the loading
of a new bunch of records in the direction you are navigating, and
unloading records from the other side
- Controlling every key for navigation and other needed purposes
- Controlling the visualization of each aspect of your info (think on
Autosizing columns, pre-programmed sizes, combination of both, assuring
that you show columns correctly and fluently ,etc)
- More things you may ancounter
Obviously I'm thinking in a component that can be used for any table, and
not just for one special table, because the programming effort to do this
type of component is too high to do it for just one table.
Don't know if you already said this because I didn't follow the entire
thread, but:
What type of validation do you need, and what is the problem you are facing
that can't be handled with the grid?
And more importantly: Is really a grid what you need? why can't you use an
input form with navigation keys that scrolls data in background?
Best Regards!
El lun., 7 ene. 2019 a las 6:20, Gene Wirchenko (<genew@telus.net>)
escribió:
> At 08:13 2019-01-06, <juergen@wondzinski.de> wrote:
> > >> I want to create my own grid
> >
> >WHY, just WHY?
>
> Because the VFP grid does not work.
>
> >Haven't yet found a problem for which I would need a homegrown grid.
> >What can't you do in VFP's native grid, in combination with the excellent
> >container hierarchy which you could add into any / every column of a grid?
>
> Full validation of a row.
>
> I came close, but it required a lot of kludges and an innocent
> change in one place could blow it up.
>
> >Build a set of controls, save them as class, add that class to the Column,
> >change Column.CurrentControl to point to that class, set Column.Sparse to
> >.F. and presto, you can do any complicated setup and stil have the
> benefits
> >of VFP's native gridspeed.
>
> I wish.
>
> One of the things that Grid is supposedly not for is data
> entry. I need a grid that can handle that.
>
> Sincerely,
>
> Gene Wirchenko
>
>
[excessive quoting removed by server]
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/CAGQ_Ju=v1uvYPM_nOhS-B0v31PpR2nbbAzaWMknZqw2CRHEV0A@mail.gmail.com
** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
Gene
The native VFP grid can handle datahandling perfectly. Please explain why
you differ on opinion
Koen
Op ma 7 jan. 2019 om 12:19 schreef Fernando D. Bozzo <fdbozzo@gmail.com>
> Hi Gene,
>
> About this:
>
> >"One of the things that Grid is supposedly not for is data
> entry"
>
> I don't agree. Not sure about the complexity of what you need to do, but if
> you used FoxPro before VFP, you could remember that before the grid
> component was the BROWSE command with many parameters that allowed many
> validations and options for row/column, and that many validations and
> options where made exactly for that purpose, for data entry. Most of them
> have no sense for other purpose than data entry.
>
> One of my first programming challenges was to do a component exactly as you
> need it to (I'm talking about dBase III+ era), and could do it, but the
> problem was that performed horribly, too slow to navigate records and
> columns.
> I think that you could face the same problem. Do not forget that you have
> to control each and every aspect of the component, as:
>
> - Scrolling left/right controlling start and end columns
> - Scrolling top/bottom controlling start and end rows
> - Controlling the data you load/unload, because you can't load a millon
> records in memory, and this forces you to control dinamically the loading
> of a new bunch of records in the direction you are navigating, and
> unloading records from the other side
> - Controlling every key for navigation and other needed purposes
> - Controlling the visualization of each aspect of your info (think on
> Autosizing columns, pre-programmed sizes, combination of both, assuring
> that you show columns correctly and fluently ,etc)
> - More things you may ancounter
>
> Obviously I'm thinking in a component that can be used for any table, and
> not just for one special table, because the programming effort to do this
> type of component is too high to do it for just one table.
>
> Don't know if you already said this because I didn't follow the entire
> thread, but:
> What type of validation do you need, and what is the problem you are facing
> that can't be handled with the grid?
>
> And more importantly: Is really a grid what you need? why can't you use an
> input form with navigation keys that scrolls data in background?
>
> Best Regards!
>
>
> El lun., 7 ene. 2019 a las 6:20, Gene Wirchenko (<genew@telus.net>)
> escribió:
>
> > At 08:13 2019-01-06, <juergen@wondzinski.de> wrote:
> > > >> I want to create my own grid
> > >
> > >WHY, just WHY?
> >
> > Because the VFP grid does not work.
> >
> > >Haven't yet found a problem for which I would need a homegrown grid.
> > >What can't you do in VFP's native grid, in combination with the
> excellent
> > >container hierarchy which you could add into any / every column of a
> grid?
> >
> > Full validation of a row.
> >
> > I came close, but it required a lot of kludges and an innocent
> > change in one place could blow it up.
> >
> > >Build a set of controls, save them as class, add that class to the
> Column,
> > >change Column.CurrentControl to point to that class, set Column.Sparse
> to
> > >.F. and presto, you can do any complicated setup and stil have the
> > benefits
> > >of VFP's native gridspeed.
> >
> > I wish.
> >
> > One of the things that Grid is supposedly not for is data
> > entry. I need a grid that can handle that.
> >
> > Sincerely,
> >
> > Gene Wirchenko
> >
> >
[excessive quoting removed by server]
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/CACUu1StEEy0SxKUwwGJENjigEqXDF-Co0r4Q112eNMBXYcXADQ@mail.gmail.com
** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
Been watching this thread and decided to pipe in - I have to observe that I have done some pretty tricky stuff with the VFP grid. Granted some not so straight forward but subclass columns and headers etc. and you can go for broke. Not found anything that can’t be done with the VFP grid. Not to say it can do everything but I'm yet to find what that is. Spend a bit of time (a few hours) and enlightened you will be.
-----Original Message-----
From: ProfoxTech [mailto:profoxtech-bounces@leafe.com] On Behalf Of Koen Piller
Sent: Monday, 7 January 2019 11:44 PM
To: profoxtech@leafe.com
Subject: Re: AW: Custom Scrollbar
Gene
The native VFP grid can handle datahandling perfectly. Please explain why
you differ on opinion
Koen
Op ma 7 jan. 2019 om 12:19 schreef Fernando D. Bozzo <fdbozzo@gmail.com>
> Hi Gene,
>
> About this:
>
> >"One of the things that Grid is supposedly not for is data
> entry"
>
> I don't agree. Not sure about the complexity of what you need to do, but if
> you used FoxPro before VFP, you could remember that before the grid
> component was the BROWSE command with many parameters that allowed many
> validations and options for row/column, and that many validations and
> options where made exactly for that purpose, for data entry. Most of them
> have no sense for other purpose than data entry.
>
> One of my first programming challenges was to do a component exactly as you
> need it to (I'm talking about dBase III+ era), and could do it, but the
> problem was that performed horribly, too slow to navigate records and
> columns.
> I think that you could face the same problem. Do not forget that you have
> to control each and every aspect of the component, as:
>
> - Scrolling left/right controlling start and end columns
> - Scrolling top/bottom controlling start and end rows
> - Controlling the data you load/unload, because you can't load a millon
> records in memory, and this forces you to control dinamically the loading
> of a new bunch of records in the direction you are navigating, and
> unloading records from the other side
> - Controlling every key for navigation and other needed purposes
> - Controlling the visualization of each aspect of your info (think on
> Autosizing columns, pre-programmed sizes, combination of both, assuring
> that you show columns correctly and fluently ,etc)
> - More things you may ancounter
>
> Obviously I'm thinking in a component that can be used for any table, and
> not just for one special table, because the programming effort to do this
> type of component is too high to do it for just one table.
>
> Don't know if you already said this because I didn't follow the entire
> thread, but:
> What type of validation do you need, and what is the problem you are facing
> that can't be handled with the grid?
>
> And more importantly: Is really a grid what you need? why can't you use an
> input form with navigation keys that scrolls data in background?
>
> Best Regards!
>
>
> El lun., 7 ene. 2019 a las 6:20, Gene Wirchenko (<genew@telus.net>)
> escribió:
>
> > At 08:13 2019-01-06, <juergen@wondzinski.de> wrote:
> > > >> I want to create my own grid
> > >
> > >WHY, just WHY?
> >
> > Because the VFP grid does not work.
> >
> > >Haven't yet found a problem for which I would need a homegrown grid.
> > >What can't you do in VFP's native grid, in combination with the
> excellent
> > >container hierarchy which you could add into any / every column of a
> grid?
> >
> > Full validation of a row.
> >
> > I came close, but it required a lot of kludges and an innocent
> > change in one place could blow it up.
> >
> > >Build a set of controls, save them as class, add that class to the
> Column,
> > >change Column.CurrentControl to point to that class, set Column.Sparse
> to
> > >.F. and presto, you can do any complicated setup and stil have the
> > benefits
> > >of VFP's native gridspeed.
> >
> > I wish.
> >
> > One of the things that Grid is supposedly not for is data
> > entry. I need a grid that can handle that.
> >
> > Sincerely,
> >
> > Gene Wirchenko
> >
> >
[excessive quoting removed by server]
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/005f01d4a6da$f268e8f0$d73abad0$@ozemail.com.au
** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
At 03:18 2019-01-07, "Fernando D. Bozzo" <fdbozzo@gmail.com> wrote:
>Hi Gene, About this: >"One of the things that Grid is supposedly not
>for is data entry"
> I don't agree.
Neither do I, but I have seen this opinion posted many times
over the years. I do not understand it myself, but there it is.
> Not sure about the complexity of what you need to do, but if you
> used FoxPro before VFP, you could remember that before the grid
> component was the BROWSE command with many parameters that allowed
> many validations and options for row/column, and that many
> validations and options where made exactly for that purpose, for
> data entry. Most of them have no sense for other purpose than data entry.
Yes, but I had a period of time where I was not using
xBASE. That was about when the fancy browses had their day. I have
looked at BROWSE, and it does not have quite what I want.
> One of my first programming challenges was to do a component
> exactly as you need it to (I'm talking about dBase III+ era), and
> could do it, but the problem was that performed horribly, too slow
> to navigate records and columns. I think that you could face the
> same problem. Do not forget that you have to control each and every
> aspect of the component, as: - Scrolling left/right controlling
> start and end columns
I have this scrolling already working in a concept case. It
was fairly easy. I grant that this may change when I add more
feature. I do not think so though.
> - Scrolling top/bottom controlling start and end rows -
> Controlling the data you load/unload, because you can't load a
> millon records in memory, and this forces you to control
> dinamically the loading of a new bunch of records in the direction
> you are navigating, and unloading records from the other side -
Yup! It is going to be fun, but I have some ideas.
I am concerned with how the scrollbar works, but I may just
come up with my own version that bypasses the issues.
>Controlling every key for navigation and other needed purposes -
>Controlling the visualization of each aspect of your info (think on
>Autosizing columns, pre-programmed sizes, combination of both,
>assuring that you show columns correctly and fluently ,etc)
I do not plan to have every feature that Grid has, at least for
the start.
I tried to get Grid working when allowing column order to
change, and it was horrible.
> - More things you may ancounter
Quite possibly.
What I have encountered is trouble with row-level
validation. Without that, Grid is NOT what I want.
> Obviously I'm thinking in a component that can be used for any
> table, and not just for one special table, because the programming
> effort to do this type of component is too high to do it for just
> one table. Don't know if you already said this because I didn't
> follow the entire thread, but: What type of validation do you need,
> and what is the problem you are facing that can't be handled with the grid?
I can not get proper row-level validation working
consistently. I have tried and tried and tried. I keep finding
cases where it breaks. I deal with a case, and something else
breaks. It is very frustrating.
I had quite a lot of trouble to get my test case to work. I
had to experiment with events and methods, but once I got it, it
worked and did so consistently.
> And more importantly: Is really a grid what you need? why can't
> you use an input form with navigation keys that scrolls data in background?
Because some of the work that needs to be done needs multiple
rows visible at once.
[snip]
Sincerely,
Gene Wirchenko
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/15d042d9866641a883852a099cc7ceb5@mtlp000083
** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
At 04:43 2019-01-07, Koen Piller <koen.piller@gmail.com> wrote:
>Gene The native VFP grid can handle datahandling perfectly. Please
>explain why you differ on opinion
Because despite multiple efforts by me to get it to work, it
would not work.
I do not believe that Grid works. At the very least, it is so
quirky, it is very difficult to use. Given that I have been able to
learn how to use other VFP classes fairly easily, I lean to the view
that Grid is buggy.
Sincerely,
Gene Wirchenko
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/cee9014521ac7d80b138146d8c8cbf76@mtlp000086
** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
At 14:47 2019-01-07, "Darren" <foxdev@ozemail.com.au> wrote:
>Been watching this thread and decided to pipe in
>- I have to observe that I have done some pretty
>tricky stuff with the VFP grid. Granted some not
>so straight forward but subclass columns and
>headers etc. and you can go for broke. Not found
>anything that canât be done with the VFP grid.
>Not to say it can do everything but I'm yet to
>find what that is. Spend a bit of time (a few
>hours) and enlightened you will be.
I have spent *manweeks* trying to get Grid
to work for my needs. It has resisted quite effectively.
[snip]
Sincerely,
Gene Wirchenko
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/7590d97538b2309d61ca7919f6e8cce0@mtlp000086
** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
Hi Gene:
I think that I've found what you need.
You need to use the Valid event of the grid in combination with the valid
of the controls.
Please, read this chapter about grids of the book 1001 things you wanted to
know about VFP.
"Grids, the misunderstood controls:"
El mar., 8 ene. 2019 4:27, Gene Wirchenko <genew@telus.net> escribió:
> At 03:18 2019-01-07, "Fernando D. Bozzo" <fdbozzo@gmail.com> wrote:
> >Hi Gene, About this: >"One of the things that Grid is supposedly not
> >for is data entry"
>
> > I don't agree.
>
> Neither do I, but I have seen this opinion posted many times
> over the years. I do not understand it myself, but there it is.
>
> > Not sure about the complexity of what you need to do, but if you
> > used FoxPro before VFP, you could remember that before the grid
> > component was the BROWSE command with many parameters that allowed
> > many validations and options for row/column, and that many
> > validations and options where made exactly for that purpose, for
> > data entry. Most of them have no sense for other purpose than data entry.
>
> Yes, but I had a period of time where I was not using
> xBASE. That was about when the fancy browses had their day. I have
> looked at BROWSE, and it does not have quite what I want.
>
> > One of my first programming challenges was to do a component
> > exactly as you need it to (I'm talking about dBase III+ era), and
> > could do it, but the problem was that performed horribly, too slow
> > to navigate records and columns. I think that you could face the
> > same problem. Do not forget that you have to control each and every
> > aspect of the component, as: - Scrolling left/right controlling
> > start and end columns
>
> I have this scrolling already working in a concept case. It
> was fairly easy. I grant that this may change when I add more
> feature. I do not think so though.
>
> > - Scrolling top/bottom controlling start and end rows -
> > Controlling the data you load/unload, because you can't load a
> > millon records in memory, and this forces you to control
> > dinamically the loading of a new bunch of records in the direction
> > you are navigating, and unloading records from the other side -
>
> Yup! It is going to be fun, but I have some ideas.
>
> I am concerned with how the scrollbar works, but I may just
> come up with my own version that bypasses the issues.
>
> >Controlling every key for navigation and other needed purposes -
> >Controlling the visualization of each aspect of your info (think on
> >Autosizing columns, pre-programmed sizes, combination of both,
> >assuring that you show columns correctly and fluently ,etc)
>
> I do not plan to have every feature that Grid has, at least for
> the start.
>
> I tried to get Grid working when allowing column order to
> change, and it was horrible.
>
> > - More things you may ancounter
>
> Quite possibly.
>
> What I have encountered is trouble with row-level
> validation. Without that, Grid is NOT what I want.
>
> > Obviously I'm thinking in a component that can be used for any
> > table, and not just for one special table, because the programming
> > effort to do this type of component is too high to do it for just
> > one table. Don't know if you already said this because I didn't
> > follow the entire thread, but: What type of validation do you need,
> > and what is the problem you are facing that can't be handled with the
> grid?
>
> I can not get proper row-level validation working
> consistently. I have tried and tried and tried. I keep finding
> cases where it breaks. I deal with a case, and something else
> breaks. It is very frustrating.
>
> I had quite a lot of trouble to get my test case to work. I
> had to experiment with events and methods, but once I got it, it
> worked and did so consistently.
>
> > And more importantly: Is really a grid what you need? why can't
> > you use an input form with navigation keys that scrolls data in
> background?
>
> Because some of the work that needs to be done needs multiple
> rows visible at once.
>
> [snip]
>
> Sincerely,
>
> Gene Wirchenko
>
>
[excessive quoting removed by server]
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/CAGQ_JunzDhwHndjjyyZ3KZA0WR86D5=uXWtAwRyhG8+VLPTzBA@mail.gmail.com
** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
While it can definitely be fun to roll your own, I would also investigate Craig Boyd's gridextras class. It's got a ton of useful features baked in such as column sorting, export, filtering, quick reporting and so on. You basically add an instance to your form, set a few properties and call its setup method when the form instantiates.
<http://www.sweetpotatosoftware.com/blog/index.php/2008/11/25/visual-foxpro-grid-enhancements/>
--
rk
-----Original Message-----
From: ProfoxTech <profoxtech-bounces@leafe.com> On Behalf Of Gene Wirchenko
Sent: Monday, January 7, 2019 10:35 PM
To: profoxtech@leafe.com
Subject: RE: AW: Custom Scrollbar
At 14:47 2019-01-07, "Darren" <foxdev@ozemail.com.au> wrote:
>Been watching this thread and decided to pipe in
>- I have to observe that I have done some pretty tricky stuff with the
>VFP grid. Granted some not so straight forward but subclass columns and
>headers etc. and you can go for broke. Not found anything that can’t
>be done with the VFP grid.
>Not to say it can do everything but I'm yet to find what that is. Spend
>a bit of time (a few
>hours) and enlightened you will be.
I have spent *manweeks* trying to get Grid to work for my needs. It has resisted quite effectively.
[snip]
Sincerely,
Gene Wirchenko
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/7590d97538b2309d61ca7919f6e8cce0@mtlp000086
** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
Report [OT] Abuse: http://leafe.com/reportAbuse/7590d97538b2309d61ca7919f6e8cce0@mtlp000086
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/BN6PR10MB1458170213751C99A8F610C2D28A0@BN6PR10MB1458.namprd10.prod.outlook.com
** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.