Hi, Gary
Providing you have removed all the places where the General field was
used, I don't believe you have to do anything more except remove the
field from the .DBFs. The forms, reports, etc. do not store any
information about the table structures, only about the fields they are
referencing.
Suggestion: Extract a 1-record test file, delete the General field, and
try running with that to catch any leftovers.
Dan
On 01/31/12 11:40, Gary Jeurink wrote:
> The saga of a rookie fixing early mistakes continues. With this forum's
> advice, I no longer put photo's into a general field. I added one integer
> field that stores a file-No that will locate the picture. The extra field
> allows multiple records to share a photo in appropriate cases. Now I am
> ready to delete the field that contained the photos. This will make a huge
> difference on the size of this table.
>
>
>
> I have edited all views or connected tables to no longer use this field but
> am I still looking at rebuilding every form that uses this table just
> because the table record field list will change? Even if so, it will be
> worth it as the storing pictures in general fields was unreliable as they
> would occasionally swap photos with other records.
>
> Gary Jeurink
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/4F2882C0.2090600@san.rr.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.
I have several items that reference the grid so using the afterRowColChange
of the grid, and I use two different grids but with the same fields it will
take a fancy procedure to change the record source for each item before
refresh.
Why can't I just change the sort of the view.
-----Original Message-----
From: Dan Covill [mailto:dcovill@san.rr.com]
Sent: Tuesday, January 31, 2012 6:10 PM
To: ProFox Email List
Subject: Re: deleting a general field
Hi, Gary
Providing you have removed all the places where the General field was
used, I don't believe you have to do anything more except remove the
field from the .DBFs. The forms, reports, etc. do not store any
information about the table structures, only about the fields they are
referencing.
Suggestion: Extract a 1-record test file, delete the General field, and
try running with that to catch any leftovers.
Dan
On 01/31/12 11:40, Gary Jeurink wrote:
> The saga of a rookie fixing early mistakes continues. With this forum's
> advice, I no longer put photo's into a general field. I added one integer
> field that stores a file-No that will locate the picture. The extra field
> allows multiple records to share a photo in appropriate cases. Now I am
> ready to delete the field that contained the photos. This will make a huge
> difference on the size of this table.
>
>
>
> I have edited all views or connected tables to no longer use this field
but
> am I still looking at rebuilding every form that uses this table just
> because the table record field list will change? Even if so, it will be
> worth it as the storing pictures in general fields was unreliable as they
> would occasionally swap photos with other records.
>
> Gary Jeurink
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/C850A15A192349D3831472EA5F69E238@OwnerPC
** 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.
Where do you put things like biographies or recipes... descriptions etc...
-----Original Message-----
From: Eurico Chagas Filho [mailto:e28chagas@yahoo.com.br]
Sent: Tuesday, January 31, 2012 1:47 PM
To: ProFox Email List
Subject: Re: deleting a general field
Now u r ready for the next fase, where u don't use memo fields anymore...
E.
>________________________________
> From: Gary Jeurink <g.jeurink@charter.net>
>To: profox@leafe.com
>Sent: Tuesday, January 31, 2012 5:40 PM
>Subject: deleting a general field
>
>The saga of a rookie fixing early mistakes continues. With this forum's
>advice, I no longer put photo's into a general field. I added one integer
>field that stores a file-No that will locate the picture. The extra field
>allows multiple records to share a photo in appropriate cases. Now I am
>ready to delete the field that contained the photos. This will make a huge
>difference on the size of this table.
>
>
>
>I have edited all views or connected tables to no longer use this field but
>am I still looking at rebuilding every form that uses this table just
>because the table record field list will change? Even if so, it will be
>worth it as the storing pictures in general fields was unreliable as they
>would occasionally swap photos with other records.
>
>
>
>Gary Jeurink
>
>
>
>--- StripMime Report -- processed MIME parts ---
>multipart/alternative
> text/plain (text body -- kept)
> text/html
>---
>
[excessive quoting removed by server]
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/9BB3F5F71F4E4758962173DF213F9629@OwnerPC
** 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.
Not sure I understand, Gary.
You were talking about removing a General field, no longer used, from
the .DBF. You also said you had already removed all references to it.
How does "referencing the grid" get into it?
Dan
On 01/31/12 20:08, Gary Jeurink wrote:
> I have several items that reference the grid so using the afterRowColChange
> of the grid, and I use two different grids but with the same fields it will
> take a fancy procedure to change the record source for each item before
> refresh.
>
> Why can't I just change the sort of the view.
>
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/4F28CFAF.2050004@san.rr.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.
That's the thing i created a system of .dbf files that store in 255 characters fields all
the text. It's like a chain. I got some routines to save and to restore, the rest is the
same as if u had a memo.
E.
Where do you put things like biographies or recipes... descriptions etc...
>
>-----Original Message-----
>From: Eurico Chagas Filho [mailto:e28chagas@yahoo.com.br]
>Sent: Tuesday, January 31, 2012 1:47 PM
>To: ProFox Email List
>Subject: Re: deleting a general field
>
>Now u r ready for the next fase, where u don't use memo fields anymore...
>
>E.
>
>
>
>
>>________________________________
>> From: Gary Jeurink <g.jeurink@charter.net>
>>To: profox@leafe.com
>>Sent: Tuesday, January 31, 2012 5:40 PM
>>Subject: deleting a general field
>>
>>The saga of a rookie fixing early mistakes continues. With this forum's
>>advice, I no longer put photo's into a general field. I added one integer
>>field that stores a file-No that will locate the picture. The extra field
>>allows multiple records to share a photo in appropriate cases. Now I am
>>ready to delete the field that contained the photos. This will make a huge
>>difference on the size of this table.
>>
>>
>>
>>I have edited all views or connected tables to no longer use this field but
>>am I still looking at rebuilding every form that uses this table just
>>because the table record field list will change? Even if so, it will be
>>worth it as the storing pictures in general fields was unreliable as they
>>would occasionally swap photos with other records.
>>
>>
>>
>>Gary Jeurink
>>
>>
>>
>>--- StripMime Report -- processed MIME parts ---
>>multipart/alternative
>> text/plain (text body -- kept)
>> text/[excessive quoting removed by server]
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/1328105665.36669.YahooMailNeo@web160804.mail.bf1.yahoo.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.
So you require multiple tables to store memo data?
Michael Oke, II
661-349-6221
Contents of this and all messages are intended for their designated recipient.
On Feb 1, 2012, at 6:14 AM, Eurico Chagas Filho <e28chagas@yahoo.com.br> wrote:
> That's the thing i created a system of .dbf files that store in 255 characters fields all
> the text. It's like a chain. I got some routines to save and to restore, the rest is the
> same as if u had a memo.
>
> E.
>
>
> Where do you put things like biographies or recipes... descriptions etc...
>>
>> -----Original Message-----
>> From: Eurico Chagas Filho [mailto:e28chagas@yahoo.com.br]
>> Sent: Tuesday, January 31, 2012 1:47 PM
>> To: ProFox Email List
>> Subject: Re: deleting a general field
>>
>> Now u r ready for the next fase, where u don't use memo fields anymore...
>>
>> E.
>>
>>
>>
>>
>>> ________________________________
>>> From: Gary Jeurink <g.jeurink@charter.net>
>>> To: profox@leafe.com
>>> Sent: Tuesday, January 31, 2012 5:40 PM
>>> Subject: deleting a general field
>>>
>>> The saga of a rookie fixing early mistakes continues. With this forum's
>>> advice, I no longer put photo's into a general field. I added one integer
>>> field that stores a file-No that will locate the picture. The extra field
>>> allows multiple records to share a photo in appropriate cases. Now I am
>>> ready to delete the field that contained the photos. This will make a huge
>>> difference on the size of this table.
>>>
>>>
>>>
>>> I have edited all views or connected tables to no longer use this field but
>>> am I still looking at rebuilding every form that uses this table just
>>> because the table record field list will change? Even if so, it will be
>>> worth it as the storing pictures in general fields was unreliable as they
>>> would occasionally swap photos with other records.
>>>
>>>
>>>
>>> Gary Jeurink
>>>
>>>
>>>
>>> --- StripMime Report -- processed MIME parts ---
>>> multipart/alternative
>>> text/plain (text body -- kept)
[excessive quoting removed by server]
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/02E2FE69-A88F-4CD0-96B5-30AE283BC45B@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.
Yes and no. The table has two fields, code and text( C 250), if code is an integer field u
use multiple tables. But if code is a composite key, say table name and primary key, it could
be just one table.
E.
So you require multiple tables to store memo data?
>
>Michael Oke, II
>661-349-6221
>
>Contents of this and all messages are intended for their designated recipient.
>
>On Feb 1, 2012, at 6:14 AM, Eurico Chagas Filho <e28chagas@yahoo.com.br> wrote:
>
>> That's the thing i created a system of .dbf files that store in 255 characters fields all
>> the text. It's like a chain. I got some routines to save and to restore, the rest is the
>> same as if u had a memo.
>>
>> E.
>>
>>
>> Where do you put things like biographies or recipes... descriptions etc...
>>>
>>> -----Original Message-----
>>> From: Eurico Chagas Filho [mailto:e28chagas@yahoo.com.br]
>>> Sent: Tuesday, January 31, 2012 1:47 PM
>>> To: ProFox Email List
>>> Subject: Re: deleting a general field
>>>
>>> Now u r ready for the next fase, where u don't use memo fields anymore...
>>>
>>> E.
>>>
>>>
>>>
>>>
>>>> ________________________________
>>>> From: Gary Jeurink <g.jeurink@charter.net>
>>>> To: profox@leafe.com
>>>> Sent: Tuesday, January 31, 2012 5:40 PM
>>>> Subject: deleting a general field
>>>>
>>>> The saga of a rookie fixing early mistakes continues. With this forum's
>>>> advice, I no longer put photo's into a general field. I added one integer
>>>> field that stores a file-No that will locate the picture. The extra field
>>>> allows multiple records to share a photo in appropriate cases. Now I am
>>>> ready to delete the field that contained the photos. This will make a huge
>>>> difference on the size of this table.
>>>>
>>>>
>>>>
>>>> I have edited all views or connected tables to no longer use this field but
>>>> am I still looking at rebuilding every form that uses this table just
>>>> because the table record field list will change? Even if so, it will be
>>>> worth it as the storing pictures in general fields was unreliable as they
>>>> would occasionally swap photos with other records.
>>>>
>>>>
>>>>
>>>> Gary Jeurink
>>>>
>>>>
>>>>
>>>> --- StripMime Report -- processed MIME parts ---
>>>> multipart/alternative
>>>> text/plain (text body -- kept)
>[excessive quoting removed by server]
>
>_______________________________________________
>Post Messages to: ProFox@leafe.com
>Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
>OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
>Searchable Archive: http://leafe.com/archives/search/profox
>This message: http://leafe.com/archives/byMID/profox/02E2FE69-A88F-4CD0-96B5-30AE283BC45B@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.
>
>
>
--- StripMime Report -- processed MIME parts ---
multipart/alternative
text/plain (text body -- kept)
text/html
---
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/1328122076.95359.YahooMailNeo@web160802.mail.bf1.yahoo.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.
WHEN YOU RETRIEVE it, how do you know when you have all f it?
-----Original Message-----
From: Eurico Chagas Filho [mailto:e28chagas@yahoo.com.br]
Sent: Wednesday, February 01, 2012 12:48 PM
To: ProFox Email List
Subject: Re: deleting a general field
Yes and no. The table has two fields, code and text( C 250), if code is an
integer field u
use multiple tables. But if code is a composite key, say table name and
primary key, it could
be just one table.
E.
So you require multiple tables to store memo data?
>
>Michael Oke, II
>661-349-6221
>
>Contents of this and all messages are intended for their designated
recipient.
>
>On Feb 1, 2012, at 6:14 AM, Eurico Chagas Filho <e28chagas@yahoo.com.br>
wrote:
>
>> That's the thing i created a system of .dbf files that store in 255
characters fields all
>> the text. It's like a chain. I got some routines to save and to restore,
the rest is the
>> same as if u had a memo.
>>
>> E.
>>
>>
>> Where do you put things like biographies or recipes... descriptions
etc...
>>>
>>> -----Original Message-----
>>> From: Eurico Chagas Filho [mailto:e28chagas@yahoo.com.br]
>>> Sent: Tuesday, January 31, 2012 1:47 PM
>>> To: ProFox Email List
>>> Subject: Re: deleting a general field
>>>
>>> Now u r ready for the next fase, where u don't use memo fields
anymore...
>>>
>>> E.
>>>
>>>
>>>
>>>
>>>> ________________________________
>>>> From: Gary Jeurink <g.jeurink@charter.net>
>>>> To: profox@leafe.com
>>>> Sent: Tuesday, January 31, 2012 5:40 PM
>>>> Subject: deleting a general field
>>>>
>>>> The saga of a rookie fixing early mistakes continues. With this forum's
>>>> advice, I no longer put photo's into a general field. I added one
integer
>>>> field that stores a file-No that will locate the picture. The extra
field
>>>> allows multiple records to share a photo in appropriate cases. Now I am
>>>> ready to delete the field that contained the photos. This will make a
huge
>>>> difference on the size of this table.
>>>>
>>>>
>>>>
>>>> I have edited all views or connected tables to no longer use this field
but
>>>> am I still looking at rebuilding every form that uses this table just
>>>> because the table record field list will change? Even if so, it will be
>>>> worth it as the storing pictures in general fields was unreliable as
they
>>>> would occasionally swap photos with other records.
>>>>
>>>>
>>>>
>>>> Gary Jeurink
>>>>
>>>>
>>>>
>>>> --- StripMime Report -- processed MIME parts ---
>>>> multipart/alternative
>>>> text/plain (text body -- kept)
[excessive quoting removed by server]
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/CD6864DE309F498488A7C8529788FBD4@OwnerPC
** 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.
Check my routine for the case i was working on;
FUNCTION GetTexto
LPARAMETERS nCode, cText
*GetTexto( nCode, cText )
*
LOCAL cTemp, lSave, nOldArea
cTemp = []
lSave = .F.
nOldArea = SELECT()
IF !USED([Texts])
USE Texts IN 0 ORDER Codigo NODATA SHARED
CURSORSETPROP("Buffering",5,[Texts])
ENDIF
SELECT Texts
SEEK nCode IN Texts
&&Read
SCAN WHILE Code = nCode
cTemp = cTemp + Text
ENDSCAN
cTemp = cTemp + SPACE(16300 - LEN(cTemp)) && a limit
SELECT (nOldArea)
RETURN cTemp
>________________________________
> From: Gary Jeurink <g.jeurink@charter.net>
>To: 'ProFox Email List' <profox@leafe.com>
>Sent: Wednesday, February 1, 2012 7:44 PM
>Subject: RE: deleting a general field
>
>WHEN YOU RETRIEVE it, how do you know when you have all f it?
>
>
--- StripMime Report -- processed MIME parts ---
multipart/alternative
text/plain (text body -- kept)
text/html
---
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/1328138652.12277.YahooMailNeo@web160803.mail.bf1.yahoo.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.