I hope someone can help...
This one should be very easy, but I've been plugging away for more than an hour and I can't get it.
In short, I've created a UX with 2 dropdown fields: ST_NO (for Store #) and TrainingDate
The ST_NO field is populated from a SQL Server Table called "StoreInfo" (which lists every Store # and some other fields with information about the stores). In that table, ST_NO is "unique" (there is only 1 of each Store #... obviously). That's the "Parent" field
Then, I have a table called "TrainingDates" which lists all classes that have ever been scheduled. That table has a field for "ST_NO" and a field for "TrainingDate" (the date of the class). There are other fields in the table, but not used for this lookup.
Here's what I want to do: I want the user to select a "Store #" and have the TrainingDate lookup display all of the Training Dates that were scheduled for that Store.
Sounds easy enough... BUT, no matter how I configure it, after selecting the Store #, the UX "locks up" (I get Microsoft's "waiting" circle and I can't do anything unless I forcefully close Alpha Anywhere, completely and then restart it). ST_NO is a Numeric Field (in both tables and on the UX) and Training Date is a "Date" field. I thought this would be easy, but I've tried so many variations and none worked (In fact, my ultimate goal is to further filter the "TrainingDate" field to display only Training Dates that occurred during the past two weeks (without the cascading, I can get that filter to work without any problem: WHERE TrainingDate BETWEEN (Now()-15) AND Now())).
So, I can use some help from someone who can figure out why this isn't working. The images below show what I've done so far:
This is what the dropdowns look like on the form, itself:
Alpha1.jpg
This is how I've programmed the "Store #" (ST_NO) field:
Alpha2.jpg
Finally, this is how I programmed the "TrainingDate" cascading field:
Alpha3.jpg
As I said, I've tried so many variations ("explicit", choosing both fields from the same Table (TrainingDates, using DISTINCT, and many more). The problem is always the same: As soon as I choose the Store #, the whole program locks up.
If you can help, "I'll be your best friend".
Thanks,
Phil
This one should be very easy, but I've been plugging away for more than an hour and I can't get it.
In short, I've created a UX with 2 dropdown fields: ST_NO (for Store #) and TrainingDate
The ST_NO field is populated from a SQL Server Table called "StoreInfo" (which lists every Store # and some other fields with information about the stores). In that table, ST_NO is "unique" (there is only 1 of each Store #... obviously). That's the "Parent" field
Then, I have a table called "TrainingDates" which lists all classes that have ever been scheduled. That table has a field for "ST_NO" and a field for "TrainingDate" (the date of the class). There are other fields in the table, but not used for this lookup.
Here's what I want to do: I want the user to select a "Store #" and have the TrainingDate lookup display all of the Training Dates that were scheduled for that Store.
Sounds easy enough... BUT, no matter how I configure it, after selecting the Store #, the UX "locks up" (I get Microsoft's "waiting" circle and I can't do anything unless I forcefully close Alpha Anywhere, completely and then restart it). ST_NO is a Numeric Field (in both tables and on the UX) and Training Date is a "Date" field. I thought this would be easy, but I've tried so many variations and none worked (In fact, my ultimate goal is to further filter the "TrainingDate" field to display only Training Dates that occurred during the past two weeks (without the cascading, I can get that filter to work without any problem: WHERE TrainingDate BETWEEN (Now()-15) AND Now())).
So, I can use some help from someone who can figure out why this isn't working. The images below show what I've done so far:
This is what the dropdowns look like on the form, itself:
Alpha1.jpg
This is how I've programmed the "Store #" (ST_NO) field:
Alpha2.jpg
Finally, this is how I programmed the "TrainingDate" cascading field:
Alpha3.jpg
As I said, I've tried so many variations ("explicit", choosing both fields from the same Table (TrainingDates, using DISTINCT, and many more). The problem is always the same: As soon as I choose the Store #, the whole program locks up.
If you can help, "I'll be your best friend".
Thanks,
Phil
Comment