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

Set Structure

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

    Set Structure

    I am having real difficulties in setting up a short term loan application, and I am beginning to think that it is due to the way I have structured the main set. I followed the AlphaSports application as a base, and I am now thinking that the structure should have the Customer table at the head.

    One of my main problems is that I have an embedded browse on a form. Despite trying various "solutions" over the weeks, and having the set using referential integrity, showing a customers historical transactions is a bit hit and miss - adding a new record often does not get linked to the browse - yet looking at the transaction table shows each record with an incremental agreement number and the right customer in the right field.

    The current set structure is attached, and I am wondering if anyone has thoughts on the merits or principles of structures - this surely is the key to the success of any application.

    #2
    Re: Set Structure

    David

    I think a little more information is probably in order. Your table definitions, the actual screen shots showing the linking information (one to one / one to many / etc.) Even though it is possible to tell whether the linking is one to one or one to many from what you provided we can't see the underlying way you have things set up. Your best option is to make a copy of your app and post a sample here zipped up so folks can have a first person look at things(Just delete any sensitive info).

    Regards,

    Jeff
    Last edited by jkletrovets; 06-08-2007, 02:46 PM.

    Comment


      #3
      Re: Set Structure

      David, I agree with Jeff, more information is needed before meaningful advice can be offered. Tell us about the application and assume none of us know anything about "short term loan databases". In the course of your narrative answer the following questions:

      1) Is each customer given a unique identification number?
      2) Do customers potentially have more than one loan agreement? Does each loan agreement get its own identifier? Is each unique?
      3) Does the app track payments, credits, writeoffs, for each loan agreement? Is each "transaction" given a loan agreement number so it can be linked to the right loan agreement?
      4) Do customers have transaction histories, or do loan agreements?

      -- tom

      Comment


        #4
        Re: Set Structure

        Thanks for the responses.

        I am really aware of the generosity of many of the members here, and am conscious that at times some posters try to get a fully blown application for free and with little input.

        For this reason, and that my application at present is still pretty basic compared with some zipped files I have seen from others, I didn't post it.

        So, as requested, attached it is - and I bet you'll work out from the layout whose knowledge I have used already as a base :-)

        The basic application is to account for and keep track of short term loans of 31 days, and these are sometimes rolled over on payment of a fee for additional periods of 31 days. A customer may have more than one current agreement at any one time. If an agreement is repaid early, discount is given. e.g. loan of 200, they get 174 cash. if repaid early, say halfway though, they only need to repay 187.

        To answer your questions, Tom,

        1) Is each customer given a unique identification number?
        2) Do customers potentially have more than one loan agreement? Does each loan agreement get its own identifier? Is each unique?
        Yes to all, and can be "unique" only in amount and more rarely percentage.

        3) Does the app track payments, credits, writeoffs, for each loan agreement? Is each "transaction" given a loan agreement number so it can be linked to the right loan agreement?
        My intention is that eventually there will be full tracking, and as customer will sometimes have more than one current agreement, a figure as soon as their record is shown that will give total current exposure for the company.

        At present it is pretty basic, with the fields tr_FeeIf used for the agreement as the contract interest and Tr_Feepdf for the fee actually levied.

        4) Do customers have transaction histories, or do loan agreements?
        I have assumed that the transaction histories will be customer based.


        I have tried an embedded form in the transaction menu, but the agreement number wouldn't increment, but it did increment if I called the subform from a button. I have tried various combinations of tick boxes in the field rules to ensure incrementation, but this is hit or miss. I'm pretty sure that I am missing some xbasic code - however my knowledge of this is limited, though I am going through the tutorials and know more than I did a month or so ago (like I didn't know what a "dim" was!!).

        In a nutshell, I suppose I am trying to do a flying application when at present I am limited to working with a zimmer frame. I'm happy to keep working at it (I have to - there isn't anything in the market that I can see that will do what I want) but some input would really be appreciated.

        David

        Comment


          #5
          Re: Set Structure

          It may be a mistake to think of customers having transactions. Better to think of customers having loan agreements, and loan agreements having transactions. This permits you to easily produce reports that show all the transactions for a loan agreement, as well as all transactions for a customer. The transactions table would hold foreign keys linking to both customer and also loan agreements.

          Comment


            #6
            Re: Set Structure

            Originally posted by Tom Cone Jr View Post
            It may be a mistake to think of customers having transactions. Better to think of customers having loan agreements, and loan agreements having transactions. This permits you to easily produce reports that show all the transactions for a loan agreement, as well as all transactions for a customer. The transactions table would hold foreign keys linking to both customer and also loan agreements.
            Thanks Tom,

            I see the logic for this, and I guess the basic set structure for this would be as attached.

            Comment


              #7
              Re: Set Structure

              Pleased to say that my payday loan application is taking shape after many hours of try this, try that.

              The customer side is quite usable, though the form is pretty rough and needs more time to tidy it up. Also, it lack a "salutation" field for writing personalised letters from boiler plates that are set up.

              The actual transaction side has been the biggest headache, but comparing to what I did just a month or so ago, my learning curve has grown significantly.

              The set structure and related tables are the key - and were wrong at the start. This is so important - trouble is, a newbie like me knows what they want to achieve, but doesn't know how to get there until they climb a few steps and can see over the parapet. Thanks Tom for your pointer on set structure. I haven't developed the transaction within agreement side yet, as I thought it would be a bridge too far - I want to get the basics working first!

              So, attached is the current status of my application with some live data (I have de-personalised all customer details, of course). I am learning all the time but would appreciate any input to speed up my learning curve.

              Comment

              Working...
              X