|
[x]
Posted via EE Mobile
|
|
| Search, ask, and monitor your questions on the go with EE Mobile. Visit Experts Exchange from your mobile device and never be out of touch again. |
|
|
|
|
|
[x]
The Solution Rating System
|
|
| With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating. - The Grade of the Solution
- The Zone Rank of the Expert Providing the Solution
- The Number of Author and Expert Comments
- The Number of Experts Contributing
- The Feedback of the Community
Your Input Matters Because of the way the system is set up, the most important variable in this equation is you. As a member of Experts Exchange, you are able to cast your vote on the quality of the solutions in regard to how complete, accurate, helpful and easy to understand each solution is. When you provide your feedback, each rating is adjusted accordingly. So, if you see a solution that has a poor rating that you think is a good solution, let us know by rating it. As you do, the rating will be adjusted and will become more accurate for other members of our site. If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support. Thank you! |
|
|
|
|
Asked by careybroph in FileMaker Pro Database
I have an MS Access database that receives data scanned from forms. That part is working just fine. However, we have a researcher who wants his data exported to a FileMaker Server database. We installed the appropriate ODBC drivers and created the links from MS Access to the tables in FileMaker. However, when we use queries to try and push new records from MS Access into the FileMaker tables, we often get errors that seem to be related to null values in the MS Access tables. These are NOT key fields, they are just data fields. For some reason, FileMaker won't accept them. Talk about a PITA. We've found that if we use an IIF to convert nulls to " " it will import into FileMaker. However, it's impractical to do this for every field and every table. And we can't stop the presses every time a different field comes through with a null.
There must be a better way. Looking for some help... or some Advil.
Thanks in advance.
20091118-EE-VQP-93 - Hierarchy / EE_QW_3_20080625