We've been working with TFS 2010/VS 2010 pair for quite a long time. The format of the "Assigned To" field was: last_name first_name. A few days ago it suddenly changed to: first_name last_name. Currently when I want to assign a bug I have to type the exact first name (as there are many people sharing the same first name) and at least one letter of the last name. Previously only 2-3 keystrokes allowed me to find the desired person.
Two questions:
What could have changed that?
How to revert the old format?
Under Project/Team Members the people are listed in first_name last_name format. Unfortunately I can't remember what was the format before the change.
The value in the Assigned To field is the Display Name of the corresponding account in the Active Directory. So typically your sysadmin made some changes in the Active Directory.
As I said it's not a TFS issue, but an Active Directory one.
I'm not expert in AD, but if I remember correctly, the order of the first/last name is changed when you change the regional settings, or something like that.
Related
As seen on above picture, I have one date entry field and one pick date button that opens calendar.
Now I want to set a trigger that prevents user from entering date greater than 01.01.2019 and raise error that
You cannot enter date greater than 01.01.2019
but I do not want to use system date as user can change system date and than enter data.
What do you mean by saying that "user can change system date"? This is Oracle Forms, right? SYSDATE returns the database server system date, not client (i.e. user's own PC) date, so - go on and use SYSDATE, no problem with that (unless, of course, users have access to the database server, but that's another story & a huge security hole).
By the way, apart from using a trigger (that would be the WHEN-VALIDATE-ITEM), a simpler way to do that is to open item's Property Palette and use the "Highest allowed value" property, set to today.
A store has n customers and anyone can visit them any time throughout the year. Data is stored in a file. Design a data structure to find if a given person visited on a date or not.
Could anyone suggest data structure I shall use in this case?
I'd suggest this: Every customer is stored in one line while you include the customer name first and then the date. You can split them with commas or something.
These are some examples
Name,Date
Name, Date
Name|Date
Name | Date
Just choose something that will be the easiest for you to use and to retrieve the information correctly with using string .split or .substring.
The problem statement does not state whether or not a customer may visit the store numerous times during the year so assuming that they can I would use a Map data-structure, where the key is the name of the customer and the value is the set of dates the customer visited the store. The data can be stored in the file using XML.
We have a column that has NULL Record entry, so we cant opt for unchecking NULLABLE field in RPD. Scenario is, we are selecting a particular department ID in prompt and for which the column has a value (Say India) but still shows NULL in the prompt. When we take the Prompt Query fired by OBIEE and run it in SQL, it retrieves only India and NULL doesnt come into picture. Is there any other option to Remove the NULL value in prompt in OBIEE? Any reason why OBIEE shows NULL values?
See this previous post for some guidance. Not all the options will work for you since your situation is different, but it could act as a good starting point.
How to Remove Null Values from prompts in OBIEE
To summarize that link, if you have a limited number of possible values, you could chose specific column Values under Options in the edit prompt dialog box.
Also, checking the box to require user input will sometimes resolve this null value problem, however this is not always the case nor is it always possible depending on your situation.
Finally, try to go to Edit Dashboard Prompt, in Choice List Values drop-down list select SQL Results, then write the SQL statements as column name is not equals to “Unspecfied” (In this way we can remove Null’s also).
Once again, that link is for another question so not all these options are applicable here, but I have found it to be a good starting point.
Let's say I have list of persons in my datastore. Each person there may have the following fields:
last name (*)
first name
middle name
id (*)
driving licence id (*)
another id (*)
date of birth
region
place of birth
At least one of the fields marked with (*) must exist.
Now user provides me with the same list of fields (and again at least one of the fields marked with (*) must be provided). I should search for the person user provided. But not all fields should be matched. I should display to the user somehow how I am sure in the results of search. Something like:
if person matched by id and last name (and user provided just these 2 fields for the search), then I am sure that result is correct (100%);
if person matched by id and last name (and user provided other fields, which were found in the database, but were not matched), then I am sure that result is almost correct by 60%;
etc.
(numbers are provided just as example)
How can I organize such search? Is there any standard algorithm? I also would like to minimize number of requests to the database.
P.S. I can not provide user with the actual field values from the database.
It sounds like your logic for determining the quality of a match will be too complex to handle at the database layer. I think you'll get the best performance by retrieving all of the records that match at least one of the mandatory keys, calculating the match score for each of them in memory, and returning the best score. For example, if the user provides you with an id, last name and place of birth, your query would look something like:
SELECT * FROM users WHERE id = `the_id` OR last_name = `the_last_name`;
This could be a performance problem if you have a VERY large dataset with lots of common last names but otherwise I would expect not to see too many collisions. You can check this on your own dataset outside of GAE. You could also get better performance if all mandatory fields MUST match by changing the OR to an AND.
I'm working on a VB6 program that connects to a SQL Server 2008 R2 database. In the past I have always used the MSFlexGrid control and populated it manually. Now, however, the guy who is paying me for this wants me to use data-bound grids instead, which forces me to use the MSHFlexGrid control because I'm using ADO and not DAO. So, I have two questions...
First, how would I move a column in a MSHFlexGrid? For example, if I wanted the third column to appear as the sixth column in the grid, is there a simple single line of code that would do that?
Second, believe it or not, I've never had to do anything in a grid other than display the data, as is, from a recordset. Now, however, I have a recordset with some fields that contain just ID numbers that refer to records in other files - for example, a field containing an ID number referring to a record in the Customers table, instead of the field containing the customer's name. What is the easiest way to, instead of having a column showing customer ID numbers from the recordset, having that column show customer names? I thought I read somewhere that there's a way to embed a sql command in a MSHFlexGrid column, but if there is I wouldn't know how to do it. Is this possible, or is there a simpler way to do it?
TIA,
Kevin
The column order would typically be handled by your SELECT statement.
Say you have a Pies table that has a FruitID foreign key related to the FruitID in a Fruits table:
SELECT PieID AS ID, Pie, Fruit FROM Pies LEFT OUTER JOIN Fruits
ON Pies.FruitID = Fruits.FruitID
This returns 3 items: ID, Pie, and Fruit in that order.
Moving columns after the query/display operation is rarely used, but yes ColPosition can be used for that.
Wow! VB6.... Back to the future! :-)
You can move Columns using the ColPosition Property.
This article shows how you could setup the grid to display hierarchical data.
If you just want to display the customer name on the same line as the main data then that is doable as well by just creating the proper SQL for your data source. For that matter you can control the column order the same way as well.
Now, how about considering upgrading to .Net? Just kidding..... No, I'm not. OK. I am, maybe. :-)