Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 75 of 807  Not logged in ELOG logo
    icon2.gif   Re: Increment a field automatically on a new thread vs every entry, posted by Chuck Brost on Fri Apr 25 19:33:24 2008 

Ok, nevermind that one, Dumb Question I think, now that I have figured out that the field I was concerned with does not increment in a reply already.  So.. that only leaves my one question, is there somewhere that I can change the text, not the action, on the menu so that I can do a reply, but have the link list as something like "New Item".?

Chuck Brost wrote:

I may have missed it when reading the logs, if so, sorry about that, but I would like to know if there is a way to set a field, let us call it "process run"  Ok let me give you some details on this.

a process run may have several "work orders" or sets of parts/items in it, so it will have several separate entries in the log  such as:

date##, run123, part 1, quantity, comment

date##, run123, part2, quantity, comment

date##, run123, part3, quantity, comment

date##, run123, part4, quantity, comment

I thought perhaps to have them use the reply function to add the other 3 items of the same run, and that would work if I could find a way to set 'process run' to auto increment, say perhaps, when the next 'New' entry was entered.  Is there something in place that can already do this?  If this is possible, I thought I would see if I can change the button for 'New' to something like 'New Run' and reply to 'Add Workorder' or something along that line so there is no confusion when entering the data.

Any suggestions you might provide are greatfully accepted.

Chuck

    icon2.gif   Re: Increment a field automatically on a new thread vs every entry, posted by Stefan Ritt on Sat Apr 26 09:26:53 2008 

Chuck Brost wrote:

Ok, nevermind that one, Dumb Question I think, now that I have figured out that the field I was concerned with does not increment in a reply already.  So.. that only leaves my one question, is there somewhere that I can change the text, not the action, on the menu so that I can do a reply, but have the link list as something like "New Item".?

 

Unfortunately this is not possible at the moment.

icon4.gif   Extending attribute list, posted by Paul O'Shaughnessy on Fri May 2 00:58:04 2008 

Hello everyone, I am new to the forum.

I currently have an attribute which is a list. From this drop down menu, I can only access around 100 options (ELog restriction I think). How can I extend my drop down list to say 200?

Example:

Attributes = RB

Options RB = a, b, c, ...,etc.

Thanks,

Paul

icon5.gif   Mass postings, posted by mike cianci on Sat May 3 14:59:14 2008 

I am setting this up as instrument log in a multi-hospital system, where there will be multiple instruments, in multiple departments, at multiple facilities.

I am using the "Top Group" function to keep the books separate so operators from one instrument/department/facility don't contaminate another instrument/department/facility's logbook.

What I am wondering is there someway to set it up so that a system wide manager could post a message to 5 individual logbooks for 5 identical instruments at 5 different locations all at once (one ELOG server)?

I hope this made sense.  Thank you for your help.

    icon2.gif   Re: Mass postings, posted by Stefan Ritt on Mon May 5 08:44:03 2008 

mike cianci wrote:

I am setting this up as instrument log in a multi-hospital system, where there will be multiple instruments, in multiple departments, at multiple facilities.

I am using the "Top Group" function to keep the books separate so operators from one instrument/department/facility don't contaminate another instrument/department/facility's logbook.

What I am wondering is there someway to set it up so that a system wide manager could post a message to 5 individual logbooks for 5 identical instruments at 5 different locations all at once (one ELOG server)?

I hope this made sense.  Thank you for your help.

Unfortunately this is not possible at the moment. You would have to use the menu command "copy to" and enable it for the admin user. Then you create your entry, and click on "copy to" once for each location you want to copy this entry.

    icon2.gif   Re: Extending attribute list, posted by Stefan Ritt on Mon May 5 08:51:10 2008 

Paul O'Shaughnessy wrote:

Hello everyone, I am new to the forum.

I currently have an attribute which is a list. From this drop down menu, I can only access around 100 options (ELog restriction I think). How can I extend my drop down list to say 200?

Example:

Attributes = RB

Options RB = a, b, c, ...,etc.

The number of 100 options is defined in elogd.c with

#define MAX_N_LIST  100

You could try to increase this to 200, but I have no idea if you will hit some other memory limit then. So what about conditional attributes? You subdivide your list into several smaller lists, like

Attributes = Category, RB
Options Category = Cat1{1}, Cat2{2}
{1}Options RB = a,b,c,d...
{2}Options RB = e,f,g,h,...
this is then also easier to handle, as compared to select a value from a very long list.
    icon2.gif   Re: Extending attribute list, posted by Paul O'Shaughnessy on Tue May 6 14:49:54 2008 

Stefan Ritt wrote:

Paul O'Shaughnessy wrote:

Hello everyone, I am new to the forum.

I currently have an attribute which is a list. From this drop down menu, I can only access around 100 options (ELog restriction I think). How can I extend my drop down list to say 200?

Example:

Attributes = RB

Options RB = a, b, c, ...,etc.

The number of 100 options is defined in elogd.c with

#define MAX_N_LIST  100

You could try to increase this to 200, but I have no idea if you will hit some other memory limit then. So what about conditional attributes? You subdivide your list into several smaller lists, like

Attributes = Category, RB
Options Category = Cat1{1}, Cat2{2}
{1}Options RB = a,b,c,d...
{2}Options RB = e,f,g,h,...
this is then also easier to handle, as compared to select a value from a very long list.

 

Stefan,

Thanks for that advice. I have made that change to the elogd.c file, but the only problem I don't know how to compile Elog to make that change take effect. I did the stop and restart of the elog  service in windows, but that made no difference. How do I compile ELog? Sorry for my ignorance, but I am fairly new to Elog.

    icon2.gif   Re: Extending attribute list, posted by Stefan Ritt on Tue May 6 15:17:52 2008 

Paul O'Shaughnessy wrote:

Stefan Ritt wrote:

Paul O'Shaughnessy wrote:

Hello everyone, I am new to the forum.

I currently have an attribute which is a list. From this drop down menu, I can only access around 100 options (ELog restriction I think). How can I extend my drop down list to say 200?

Example:

Attributes = RB

Options RB = a, b, c, ...,etc.

The number of 100 options is defined in elogd.c with

#define MAX_N_LIST  100

You could try to increase this to 200, but I have no idea if you will hit some other memory limit then. So what about conditional attributes? You subdivide your list into several smaller lists, like

Attributes = Category, RB
Options Category = Cat1{1}, Cat2{2}
{1}Options RB = a,b,c,d...
{2}Options RB = e,f,g,h,...
this is then also easier to handle, as compared to select a value from a very long list.

 

Stefan,

Thanks for that advice. I have made that change to the elogd.c file, but the only problem I don't know how to compile Elog to make that change take effect. I did the stop and restart of the elog  service in windows, but that made no difference. How do I compile ELog? Sorry for my ignorance, but I am fairly new to Elog.

You need a C compiler to compile Elog under Windows. If you don't have one, I would suggest to follow the advice to use conditional attributes. This does not require a recompilation of Elog.

ELOG V3.1.5-3fb85fa6