Re: Problem With Pro*c



rajesh.chidambaram@xxxxxxxxx wrote:

int load_convers_data()
{
char *function = "load_convers_data";
long i;
int j;
int li_return;

char ls_scale_cnstr_dimension_uom[NULL_UOM] = "";
char ls_scale_cnstr_weight_uom[NULL_UOM] = "";
char ls_scale_cnstr_curr[NULL_CURRENCY_CODE] = "";
int li_in_season;
int li_stat_cube_ind = 0;

/* check what constraint types are defined for scaling; */
/* if "M" (mass) or "V" (volume), get target weight or dimension
uom */
/* if "A" (currency amount), get target currency code */

fprintf(fp_outfile, "ls_scale_cnstr_dimension_uom = %s\n",
ls_scale_cnstr_dimension_uom);

There is no problem in the code you have posted. There may be a problem
in the code you use to open (and declare!) fp_outfile; there may be a
problem in the part of the code where you now have only comments; or
there may be a problem in later or earlier code.
If that code is ISO C, whittle it down to the smallest compilable sample
which still has the problem, and post that here.
If that code is not ISO C, but Pro*C, do the same, but post it in an
Oracle newsgroup - this group can't help you debug Oracle Pro*C code.

Richard
.



Relevant Pages

  • Re: All programs are undefined, Re: Why this works???
    ... terms of the capabilities of a particular machine about whose details ISO ... void printat(const char *s, int x, int y, int bg, int fg) ... If this technique were not well-defined under the above circumstances, ... these programs were able to rely on the well-definedness of this technique ...
    (comp.lang.c)
  • Re: Number of weeks in year?
    ... >produce results incompatible with ISO 8601" ... >private int WeekNumber_Entire4DayWeekRule ... > StartWeekDayOfYear = StartWeekDayOfYear; ... > EndWeekDayOfYear = EndWeekDayOfYear; ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: Garbage Collection - Stop Making Trash
    ... > as soon as the ECMA standard is ratified, it will be submitted to ISO. ... int main ... pointer, it cannot be moved by the GC and will not be garbage collected. ...
    (comp.lang.cpp)
  • Re: code portability
    ... All the ISO guys had to do was - nothing at all! ... wrongly assumes long int is precisely 32 bits is already broken, ... long as you can spare the space), and don't worry about changing data ... most companies don't switch compilers too often. ...
    (comp.lang.c)
  • Re: VS2005 doesnt like its own suggestions
    ... But first, about BOOL, INT etc. ... ISO C++ can stay the same and so could int and long. ... The non-morbid reasons, which I lean to believe are the prevalent ...
    (microsoft.public.vc.language)