Alpha Software Mobile Development Tools:   Alpha Anywhere    |   Alpha TransForm subscribe to our YouTube Channel  Follow Us on LinkedIn  Follow Us on Twitter  Follow Us on Facebook

Announcement

Collapse

The Alpha Software Forum Participation Guidelines

The Alpha Software Forum is a free forum created for Alpha Software Developer Community to ask for help, exchange ideas, and share solutions. Alpha Software strives to create an environment where all members of the community can feel safe to participate. In order to ensure the Alpha Software Forum is a place where all feel welcome, forum participants are expected to behave as follows:
  • Be professional in your conduct
  • Be kind to others
  • Be constructive when giving feedback
  • Be open to new ideas and suggestions
  • Stay on topic


Be sure all comments and threads you post are respectful. Posts that contain any of the following content will be considered a violation of your agreement as a member of the Alpha Software Forum Community and will be moderated:
  • Spam.
  • Vulgar language.
  • Quotes from private conversations without permission, including pricing and other sales related discussions.
  • Personal attacks, insults, or subtle put-downs.
  • Harassment, bullying, threatening, mocking, shaming, or deriding anyone.
  • Sexist, racist, homophobic, transphobic, ableist, or otherwise discriminatory jokes and language.
  • Sexually explicit or violent material, links, or language.
  • Pirated, hacked, or copyright-infringing material.
  • Encouraging of others to engage in the above behaviors.


If a thread or post is found to contain any of the content outlined above, a moderator may choose to take one of the following actions:
  • Remove the Post or Thread - the content is removed from the forum.
  • Place the User in Moderation - all posts and new threads must be approved by a moderator before they are posted.
  • Temporarily Ban the User - user is banned from forum for a period of time.
  • Permanently Ban the User - user is permanently banned from the forum.


Moderators may also rename posts and threads if they are too generic or do not property reflect the content.

Moderators may move threads if they have been posted in the incorrect forum.

Threads/Posts questioning specific moderator decisions or actions (such as "why was a user banned?") are not allowed and will be removed.

The owners of Alpha Software Corporation (Forum Owner) reserve the right to remove, edit, move, or close any thread for any reason; or ban any forum member without notice, reason, or explanation.

Community members are encouraged to click the "Report Post" icon in the lower left of a given post if they feel the post is in violation of the rules. This will alert the Moderators to take a look.

Alpha Software Corporation may amend the guidelines from time to time and may also vary the procedures it sets out where appropriate in a particular case. Your agreement to comply with the guidelines will be deemed agreement to any changes to it.



Bonus TIPS for Successful Posting

Try a Search First
It is highly recommended that a Search be done on your topic before posting, as many questions have been answered in prior posts. As with any search engine, the shorter the search term, the more "hits" will be returned, but the more specific the search term is, the greater the relevance of those "hits". Searching for "table" might well return every message on the board while "tablesum" would greatly restrict the number of messages returned.

When you do post
First, make sure you are posting your question in the correct forum. For example, if you post an issue regarding Desktop applications on the Mobile & Browser Applications board , not only will your question not be seen by the appropriate audience, it may also be removed or relocated.

The more detail you provide about your problem or question, the more likely someone is to understand your request and be able to help. A sample database with a minimum of records (and its support files, zipped together) will make it much easier to diagnose issues with your application. Screen shots of error messages are especially helpful.

When explaining how to reproduce your problem, please be as detailed as possible. Describe every step, click-by-click and keypress-by-keypress. Otherwise when others try to duplicate your problem, they may do something slightly different and end up with different results.

A note about attachments
You may only attach one file to each message. Attachment file size is limited to 2MB. If you need to include several files, you may do so by zipping them into a single archive.

If you forgot to attach your files to your post, please do NOT create a new thread. Instead, reply to your original message and attach the file there.

When attaching screen shots, it is best to attach an image file (.BMP, .JPG, .GIF, .PNG, etc.) or a zip file of several images, as opposed to a Word document containing the screen shots. Because Word documents are prone to viruses, many message board users will not open your Word file, therefore limiting their ability to help you.

Similarly, if you are uploading a zipped archive, you should simply create a .ZIP file and not a self-extracting .EXE as many users will not run your EXE file.
See more
See less

Finding and reporting on empty fields

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Stan Mathews
    replied
    Re: Finding and reporting on empty fields

    See if you like this approach.

    Code:
    dim answer as p
    answer.count = 0
    fld_list = ""
    tbl = table.open("item")
    flds = table.fields_get()
    FOR i = 1 TO flds
    	fld_name = tbl.field_get(i).name_get()
    	tbl.field_statistics(fld_name, answer)
    	IF answer.count = 0
    		ui_msg_box("Warning","Table is empty")
    		end
    	END IF
    	fld_type = typeof(answer.maximum)
    	SELECT
    		CASE fld_type = "C"
    			IF answer.maximum > ""
    				fld_list = fld_list + fld_name + ", "+fld_type+", "+answer.maximum + crlf()
    			END IF
    			
    		CASE fld_type = "N"
    			IF answer.maximum > 0
    				fld_list = fld_list + fld_name + ", "+fld_type+", "+alltrim(str(answer.maximum)) + crlf()
    			END IF
    			
    		CASE fld_type = "D"
    			IF answer.maximum > {}
    				fld_list = fld_list + fld_name + ", "+fld_type+", "+dtoc(answer.maximum) + crlf()
    			END IF
    			
    		CASE fld_type = "L"
    			IF answer.maximum = .T.
    				fld_list = fld_list + fld_name + ", "+fld_type+", "+".T." + crlf()
    			END IF
    	END SELECT
    NEXT i
    tbl.close()
    ui_msg_box("Found",""+fld_list)
    A bit of testing reveals that date fields are reported as character.
    Last edited by Stan Mathews; 10-30-2008, 10:00 AM.

    Leave a comment:


  • Ted Giles
    replied
    Re: Finding and reporting on empty fields

    You are a star! I'll try this out first thing tomorrow. What's the weather like out West?

    Leave a comment:


  • Stan Mathews
    replied
    Re: Finding and reporting on empty fields

    This should work for all data types.

    Code:
    fld_w_values = ""
    tbl = table.open("yourtablename",FILE_RW_EXCLUSIVE)
    flds_list = tbl.field_name_get()
    FOR each fname in flds_list
    	query.filter = ""
    	query.order = "invert("+fname+")"
    	query.options = ""
    	query.description = "Check"
    	tbl.query_create()
    	tbl.fetch_first()
    	thisfield = "tbl."+fname
    	IF isnotblank(thisfield)
    		fld_w_values = fld_w_values+fname+","
    	END IF
    	tbl.query_detach("Check")
    next
    tbl.close()
    ui_msg_box("Found","Values in "+ fld_w_values)
    'or trace.writeln(fld_w_values)

    Leave a comment:


  • Ted Giles
    replied
    Re: Finding and reporting on empty fields

    Thank's Stan. Trouble is the number of fields/columns I need to go,through.
    There are 27 tables with up to 250 fields in each - all different names e.g.
    ** O_ROTA_PATTERN_GROUPS.PAG_OVERLAP_DAYS
    (It's in an Oracle table at present).
    Is there a way of "incrementing" the fields, or reading the names into an array and cycling through them do you think?

    Leave a comment:


  • Stan Mathews
    replied
    Re: Finding and reporting on empty fields

    I would sort the table descending by each field in turn and check that the field in question in the first record in the sort order is not blank.

    Code:
    fld_w_values = ""
    tbl = table.open("yourtablename",FILE_RW_EXCLUSIVE)
    query.filter = ""
    query.order = "invert(firstfieldname)"
    query.options = ""
    query.description = "Check"
    tbl.query_create()
    tbl.fetch_first()
    IF tbl.firstfieldname > ""
    	fld_w_values = fld_w_values+"firstfieldname,"
    end if
    tbl.query_detach("Check")
    query.filter = ""
    query.order = "invert(secondfieldname)"
    query.options = ""
    query.description = "Check"
    tbl.query_create()
    tbl.fetch_first()
    IF tbl.secondfieldname > "" 'or other test for numeric, date, logical
    	fld_w_values = fld_w_values+"secondfieldname,"
    end if
    tbl.query_detach("Check")
    tbl.close()
    ui_msg_box("Found","Values in "+ fld_w_values)
    'or trace.writeln(fld_w_values)
    Last edited by Stan Mathews; 10-29-2008, 11:53 AM.

    Leave a comment:


  • Ted Giles
    started a topic Finding and reporting on empty fields

    Finding and reporting on empty fields

    Has anyone got any ideas how to report on fields in a table with data present?
    I know the table name, and the field names.

    I need to compare migrated data with available data and identify what didn't get migrated to a new application. (Under the control of the supplier).

    I plan to scan the table and report the name of each field which has data present - but only once.

    So, if any field in a table of 200,000 records has data, I need to know the name of that field.

    As soon as a field has been identified as having data, the current search can stop and the next field interrogated.

    My simple logic would be;
    Read record1, field1
    If Data found - report
    If not found
    Read next record field1
    If data found - report

    Once a field has been identified with data, read next field staring at record 1.

    It's driving me nuts as I'm sure there is a simple way to do this using the Query function.

    Ted
    7 hours in the car today as the M40 was closed. First bit of cold weather and it's mayhem!
Working...
X