Build a report having below requirement:
Fields:
EmployeeID
Worker
Primary Position
Business Title
Location
Username
Hire Date
Original Hire Date
Termination Date
Hire BP Completion Date
Termination BP Completion Date
Selection Criteria:
Worker must be either active or on leave or (termination date within last 30 days)
Build above report and let me know once it's done
Related
I'm working with loopback , but now i want to perform some operation on my data after a certain time automaticaly
Precioulsly I have a model called Canal and my model has a field beginDate and endDate of type Date, beginDateis set to today date , and endDateis set to beginDateplus two dates , so I want to delete Canal whom endDate is expired
Any ideas how to process ?
You can use node-schedule to add something like a cron job and run it in specific time each day and delete expired Canals.
You should define it as a boot script in LoopBack.
Let's say I have a table called adverts with the following fields: advert_id, name,date_created description, duration, status, user_id, cat_id.
Let's say a user puts a duration of 1 week in the duration field and its status is set to active. After a week has passed, the status is set to inactive in the table.
Can anyone tell me if it's possible to do this with asp.net 4.0 code using visual basic in visual studio 2010 with web forms?
I don't see a reason to update a status at all. Instead of (or in addition to) duration, store the datetime the status is to be set to active (current datetime plus duration). The application can then consider values less than the current datetime as active without having to actually update the row.
If desired, you can still derive the active status as a column the query or as a derived column in the table. For example:
SELECT CASE WHEN active_date <= GETDATE() THEN 'Y' ELSE 'N' END AS active
FROM dbo.adverts;
We are selling a product using Drupal Commerce that will renew yearly, but not automatically (expensive, users will likely use POs). Right now, after purchase, they will receive the appropriate role based on their purchase for 1 year.
If they pay before the end date, I would like them to get an additional, non-overlapping year.
I would like a solution that is independent of payment type because some things will be done manually.
I had implemented such a solution before. There was a subscription for a year,two years & three years. The problem was how to maintain the subscription limit & how to extend it.
The solution was creating a hidden field within for every user. When a user first buys a package for a year we programatically make a entry of the end timestamp in the end field. When he buys one more package the current timestamp value of the field is added by additional timestamp
timestamp = timestamp + 1years timestamp
or
timestamp = timestamp + 2years timestamp
Hope this helps you
we have a bio metric software for attendance, you press finger over sensor and it puts you IN/OUT time in SQL database, it's desktop app but boss asked me to make same but Web Application in asp.net MVC, now we have 2 tables
tblEmployee
SerialId
EmpId
EmpName
DepId
tblAttendance
AtdId
EmpId (FK)
Time(IN/OUT)
Date
now problem is that When i come into office then it put new record in attendance table and when i leave office then it again put whole record for OUT time in attendance table, it's using same field TIME for IN and OUT both. So thinking to solve this issue like Keeping single record for single day and only changing IN/OUT time ?
This look like normal behavior to me, but still if you want to achive what you have asked, you could change the table definition like this -
tblAttendance
AtdId
EmpId (FK)
Date --Just the date for every day
Time_IN
Time_OUT
Now you need to figure out which swipe it is - IN or OUT and update the particular value. For every IN there would be a new row - which you can control for a particular DATE - as in one row per DATE - Composite Primary Key - AtdId, EmpId (FK), Date
Note - Over the time the above approach will slow down the punch IN/punch OUT process. It'll take comparatively longer to register the swipes. Your current DB structure is more apt for long term usage. If you want to display the data in any particular format, you should rather design views as per your requirements.
I am making a fees collecting module for a college in php, On submit, I want to echo voucher number, every time the voucher number should be +1 to previous voucher. And every day the voucher number should start from 1.
Just create a DB table to store the current voucher number and the date.
On every submit you :
Check if the date is today's date. If not you reset the voucher number
Increment it
And try a little research before asking next time.