cdsaenz wrote:Fixed. I guess. Replace Journals.prg with attached source.
attached
Saludos
--
Esgici
Moderator: Rathinagiri
cdsaenz wrote:Fixed. I guess. Replace Journals.prg with attached source.
All right, thanks.cdsaenz wrote:Take a look again plz. It seems that PRG files are not allowed attachments.
Oh, yes; sorry, I'm missed this point.cdsaenz wrote: Did you look at line 125? Do you have any idea why frmJournals can't be referenced at that line?
Yes, I know you have two form; confusing is only on its namescdsaenz wrote:Oh no, really I have two forms:
- frmJournals is where I show the whole lot of journals.
- frmJournal is where I just edit one of them.
So after editing and closing frmJournal, what I want is to refresh frmJournals, the one with the whole journals file.
But naming is confusing I know.. I'll play a little around it.
No, itsn't right; Harbour expanded variable name's length; AFAIK up to 64cdsaenz wrote:Thinking back it must be something with the eight characters limit for variable names right? I guess so.
Problem isn't on if its are different or not, problem is on readability and this meant easy to understand.cdsaenz wrote:In my real project, name of the forms are different and they are working allright. Names of the forms are:
AsientoEdit
Asientos
If you observe the first eight (AsientoE and Asientos) are different. So that was it I assume.
Why is code readability such an important issue in this coding standard? First of all if a team of programmers is working in the same source code files, you need to have an agreement on how the layout of the code should look like. Even if you agree to don’t have general code layout, that’s still an agreement. This coding standard has got a lot of agreements about coding style and you can decide per item to use it or not.
Second, the better the code is readable, the better can be maintained. This reduces the chance of bugs and simplifies debugging the code and fixing the bugs.