Search these areas:
Help
Support Forums
Product Info



-Introduction
-DataWeb: What's New
-Creating an Application
-The DataWeb Designer
-Application Management
-Data Tables
-Data Tables
-Views
-Templates
-Components
-Data Analysis
-Members
-Security
-Importing
-Exporting
-FTP
-JavaScript
-Object Model
-Full-Text Search
-Domain and Email Hosting
-HotBlock Modules
-Account Management
-Glossary
-New Responsive UI Module





DataWeb Help
Support Forums
Tutorial
Script Library
Knowledge Base

Home > Support

Support Forum



Having a hard time get going
rodrigos asked:
I imported three ACCESS tables. They have relationships which were not preserved, I can't figure out why (they are one-to-many). Then, I want to produce a report (Critical Items) showing all items that are critical ("Yes") and are used on bills of materials; if they are used, display all the BOMs where each critical item is used. I have a simple ACCESS query that does this for me, I'm not sure how to accomplish this here. I'm very excited about this technology and I'm looking forward to use it seriously.

Regards,

Rodrigo
 
  marki responded:
  I am not sure why your relationships were not preserved.

If your data is not too sensitive, you can upload your mdb to a westside web and give read access to someone at westside (send mail to support@westside.com)

If you'd rather not do that, here are some possible reasons why relationships may not have been preserved:

1) The relationships were used in queries, but are not explicitly shown in the relationships window in Access.

2) The tables used multi-field primary keys. Westside currently only supports single field primary keys.

3) The tables don't have primary keys.

Once you do have a database with relationships, you can create a query like this:
1) Create a grid view of the items table.
2) Include fields from the BOM table by adding fields to the items data region and clicking on the hyperlink for the BOM lookup field. You'll see a list of fields in the BOM table and you can check the ones you want to see.
3) You can filter your view based on the value of Critical
 
  matthewb responded:
  One particularly confusing variety of this issue is when the column on the "one" side of the relationship is unique but is not the primary key.  
  rossb (DataWeb) responded:
  DataWeb considers this issue closed.
If you have additional questions or comments about this issue, please open it again.
If you have questions about a different topic please open a new support question.

Thanks,
DataWeb Support
 
  rossb (DataWeb) responded:
  This issue is open.  
  dougl responded:
  After further investigation, it looks like Matthewb is right: Rodrigos original Access database contained lookups to a text-field in a table that wasn't the primary key.

Rodrigos and I will work on a solution that will repair these relationships/get his web working correctly.
 
  dougl responded:
  Rodrigos:

I'm not sure if you're getting them mail I've sent to both your email addresses. I've gotten a lot of "bounced" mail messages from your mail servers. Please add a message to this discussion to let me know the best/most reliable way to communicate with you.

Thanks,
Doug.
 
  dougl responded:
  ACCESS is much better at changing the primary key of a table with data in it. Change the primary key in your mdb and re-import it.  
  dougl responded:
  DataWeb considers this issue closed.
If you have additional questions or comments about this issue, please open it again.
If you have questions about a different topic please open a new support question.

Thanks,
DataWeb Support
 
  Please Log On
or create your own DataWeb Account.
Affiliate | Partner | Terms of Use | Privacy Policy | Contact Us | Pricing | Bring DataWeb In-House    
DataWeb, 720 North 10th Street, A #145, Renton, Washington 98057 *425-583-5970* Fax 484-770-4706* Email Us