I would like to design a database application that can be used by multiple salespeople. A sales person would collect data from there various clients out in the field and would on an daily or weekly bases, somehow (preferably by email) send the data collected to a someone at the main office who in turn would then update this data to an existing database. The salesperson in the field would always have there information on there laptop, but the main computer would have information from several salespeople in it's database, and as individual data is collected, it is updated to the main computer's database. Can this be done?
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 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:
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:
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.
- 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
Multiple users with multiple databases
Collapse
X
-
Re: Multiple users with multiple databases
The salesperson would collect there individual data, then lets say every Sunday would submit there previous weeks data which in turn would be "added" to an existing database on a central computer. When the salesperson is in the field, they often have no access to the internet, so trying to login into a web application would next to impossible.
Comment
-
Re: Multiple users with multiple databases
create some code that converts the data into common a ascii text file.
Also, create some code that reads the ascii and populates the db
The operations genie can design both for you.There can be only one.
Comment
-
Re: Multiple users with multiple databases
Jon,
If you write the tables the same for the sales people as the main office. You can send a text email from the sales people to the main office and the main office canrecieve it, fill in the new form in the main database. there would need to be no interference from or very much time taken by anyone at the main office.
Each customer info would be sent as a seperate email to one main email account. Same email account for all sales people.
This works! I do something similar now, but not similar enough for you to use.
This way the office is updated imediately if needed.
I think this is what the others are trying to tell you.
.
Comment
-
Re: Multiple users with multiple databases
Originally posted by Stan Mathews View Post...The operations genie can design both for you.
You make it sound so easy. ;)
Comment
-
Re: Multiple users with multiple databases
Originally posted by jbk View PostDoes anyone know of any examples for A5 that may be similar to what I'm trying to accomplish.
Stan gave you the answer. Go to the operations tab of the control panel...
Comment
-
Re: Multiple users with multiple databases
In the Help file there is a whole page which explains about Email Automation.
This should do just what you want.Regards
Keith Hubert
Alpha Guild Member
London.
KHDB Management Systems
Skype = keith.hubert
For your day-to-day Needs, you Need an Alpha Database!
Comment
-
Re: Multiple users with multiple databases
I also have a remote data entry feature to an application. As with Dave, it is so application specific that it would not be of use to anyone else.
I would certainly keep thinking if there is a way to do this with a web app. If they are going to email the data, they have internet access. A cell based data cards will also give you internet access anywhere you can make a cell call.
A web app solves many synchronization issues you can have with a batch process. Salespeople still have access to only their data. I would try hard to see if there is a way for a web app to work.
Bill.
Comment
-
Re: Multiple users with multiple databases
If I were doing this I would create an "Update Database" for each salesperson. They'd have their sales database on their PC plus an empty Update Database. When they're ready, they'd push a button in thier app and any new records (flagged as new, or updated - because current info could change) could be copied to the update database. Each time the sale person goes to copy records to the update database, code checks to see if it's empty... it not the sales person get to choose to empty it.
The Update database tables are added and dropped via code.
Once updated, the update database could be emailed to the central office where a person would take that database, unzip it, put it in a "sales person" folder - to keep it unique - and run an update routine on the main app to add the tables from the update database, copy the records over, and drop the tables.
Comment
-
Re: Multiple users with multiple databases
Hi,
I just realised, Jon saidsomehow (preferably by email)
This then would be a web app without all of the issues of who does what and when.Regards
Keith Hubert
Alpha Guild Member
London.
KHDB Management Systems
Skype = keith.hubert
For your day-to-day Needs, you Need an Alpha Database!
Comment
Comment