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

Another best practices question

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

  • tcampb
    replied
    RE: Another best practices question

    Bill,
    That's right.
    In A4, I am currently using a temp table for the results of the search(query) then writing the references (account number, record number, invoice number) to another table and saving the results. This locks in the references. I think the problem (re-query vs viewing in a set) would present when I need to go back at a later date and look at the invoice. My other concern is not having an exact EXISTING copy of what was mailed to the client. That is not to say that there would be any reason for the results to change, in fact they probably wouldn't, but... call me paranoid.
    I am only using about 7000 records in development but the production database holds about 100,000 records. I'm not sure what the speed implications are yet.

    My thought for simpler was to perhaps just lock in the date range, filter with that, then query by account number to REproduce the invoices???

    Thanks
    tc

    Leave a comment:


  • Bill Warner
    replied
    RE: Another best practices question

    You said, "But, then each time I look at an invoice, It would need to be re-queried." I've found that creating a temp table (maybe you're already doing this?) is very fast, and as long as you're using the same group of records, you could access the temp table instead of running the query again (assuming the query takes a long time?).

    Leave a comment:


  • tcampb
    started a topic Another best practices question

    Another best practices question

    Hi, it's me again.

    Another general overview type question. In A4, I built the invoice module of my application to do alot of behind the scenes batch type processing, field filling, using temp tables and the like. Apply search to big data file, write
    pointer(recno()) fields to an intermediate table linked to customer and invoice header. It seems to me that I get a bit of redundancy that sort of "locks in" the invoices. (2 sets, 5 independent tables, 18 or so scripts)

    I'm wondering about perhaps a simpler approach. I already get a print date and do some math to create a print range. Then apply this to big data table to draw out records. Perhaps if I only save the dates (range)? But, then each time I look at an invoice, It would need to be re-queried,
    as opposed to set view.

    We do repetetive service work and track our inventory by the address at which the work was performed.

    Sorry for the stream of conscienceness (sp?).
    Any broad thoughts on how to structure this? What are the best practices for bringing realtime inventory data entry to invoices?

    Thanks
    tc
Working...
X