how to read keystorkes of keyboard in oracle forms 6i - oracleforms

Hell EveryOne I am Trying to Read Key strokes in oracle forms 6i.My Requirement is that when i press any key or combination in oracle forms 6i then i want to display which key is pressed.Is there anyway to detect this in oracle forms 6i.

Related

Making unique Composite index in Sharepoint 2013

I am developing a access database front-end, where the database resides in SharePoint list. There is a Attendance Table with AttDate and StaffID columns apart from other columns.
Want to achieve: Only one record is added per staff for a day. i.e. only One Attendance is recorded in a day. When user tries to enter attendance of same staff again on same day, he should get error.
When the back-end was in Access file, I had created an index with 2 columns, and made the index "allow unique values only". The screen looks like this.
Now when, I am moving my back-end to SharePoint, I was expecting same functionality. But, moving Tables to SharePoint using Access 2013 wizard did not create the index. Hence I thought creating it manually will solve the problem. So, I created an index with 2 columns, See screenshot below.
When I entered data, it still allows multiple values , see Screenshot
below
Please help, as to what can be the solution to this problem. I am
allowed to change existing table structure, if the solution so
demands. Any workaround will also be helpful.
SharePoint indexing is more about making it faster to retrieve and search for items in SharePoint. It has nothing to do with unique constraints.
You're going to have to add something to your SharePoint instance that will perform this check for you.
You haven't mentioned whether you're using SharePoint on-line or on-premise. You do say that you're using the Access front-end. This typically means you'll need to use an event receiver which will involve C# (or VB.NET) programming.
Workflows wouldn't prevent the duplicate row from being saved
JavaScript would help if using SharePoint UI, but won't prevent services
You do mention that you're using an Access front-end. Maybe you can add some business logic in your Access file?
Hope this helps

how can we integrate help file in oracle forms 11g

I need to show help contents in oracle forms 11g.
I can see "Help book title" property in form's property palette and "Help Book Topic" property in oracle forms items. But I am not able to get any information regarding how to use this.
Please help.
Those properties are no longer supported in Oracle Forms Services. They are relics from the client-server days (Oracle Forms 6i and earlier).
So, you're pretty much on your own for implementing help files. I suggest creating HTML files that are accessible from your Forms server and using the web.show_document() built-in to display them, perhaps from a menu item or button.

Exporting Foreign Key Definitions as DDL Statements from MS Access

I am trying to implement source control for my MS Access project (using git). The question, How do you use version control with Access development?, helped me setup exporting/re-loading from text for queries, modules, forms, macros and reports. For the table schema, I attempted to export create statements using the code from this other question, Table Creation DDL from Microsoft Access. I was then able to load tables back into Access using these create statements. Unfortunately, foreign key definitions are not exported. Is there a way to export the foreign key references as DDL statements?
I use OASIS for this purpose. Although this is originally designed to work with Subversion (TortoiseSVN), ignoring the SVN part makes this tool very helpful for Mercurial as well, so why not Git, too? It's not free, but it's worth the (small) price.
In short words, OASIS exports and imports every Access object to and from files (one file per object), avoiding the partially crazy implementation of MSSCCI ("tables and other objects"). Having those files, you may use any version control system you want.

Is there a MySQL client on OSX that has great useability?

I'm looking for a MySQL client on OSX with a mac design philosophy. I've been using mac programs for too long and can't really go back to windows designed programs. I'm looking for a program that has a sleek UI and great convenience for common tasks. (For example, ss there a client that allows you to delete a row by selecting it after a select query?)
I've already read the other two SO threads, nothing there.
Price does not matter.
Have you tried Sequel Pro yet?
Querious is really awesome.
If you're open to web apps, there is SQLBuddy, which is all slick and AJAX-y.
You may like SQLPro for MySQL.
The app has a few neat features such as:
Auto-completion and syntax highlighting.
Tabbed based interface.
Query primary key detection and the ability to edit results inline.
Support for executing multiple queries at once.
Quick access to tables, columns and more.
Use one of the pre-built themes, or customize your own.
Exporting options to CSV, JSON and XML.
Importing from CSV, JSON or XML.
There is a seven day trial available via the website.
Disclaimer: I'm the developer. Or if you pop me an email, I can send a free promo code.
Also, in direct response to
(For example, is there a client that allows you to delete a row by selecting it after a select query?)
SQLPro for MySQL will detect your table and primary keys from an executed query. As long as all the primary keys are available you can edit, delete or insert directly from a result set.

Data macros in Access2010: triggers?

I've heard on the grapevine that the forthcoming Access2010 has a Data Macros feature which will for the first time add trigger-like functionality to Access data engine tables. Does anybody have an further details on this? For example, can they created in code (ACEDAO, SQL DDL, etc)? Does the Data Macro run if the data is modified from outside of the Access user interface e.g. via ODBC, OLE DB, etc?
Ok, a bit more information.
Does the Data Macro run if the data is modified from outside of the Access user interface e.g. via ODBC, OLE DB, etc?
Yes it does.
These true triggers are at the data engine level. So, using ado, dao or even editing the tables in table view in ms-access means the triggers will fire. These triggers would also include the scenario where you don’t even have ms-access installed on your computer.
You will of course need JET installed (for the remainder of this article I will use the term ACE). Remember it was only in access 2007 that the access team received ownership of JET. They are now free to enhance this engine for their needs. We started to see some changes to ACE in 2007 and now we will see a LOT more changes for 2010. Some of these features are still NDA for me…but I will spill as much as I can here.
For example, can they created in code (ACEDAO, SQL DDL, etc)?
In code, perahps, but not with SQL ddl. The triggers are not sql commands. Keep in mind that for Oracle, or Sql server or MOST systems in the marketplace they all tend to have their OWN custom language for their triggers anyway.
In the new ACE you thus will write what is called a data macro. You use the macro editor in ms-access. These are old fashioned access macros, but the editor has been completely re-done. The new macros also have subroutines, looping, if then else blocks and a type of recordset. Remember, we received the ability to create temp variables in 2007 macros. In 2010 this is extended to also include local variables and above new features.
The syntax for existing macro commands is the same as previous versions. However, we have a new slick IDE along with all those above cool commands added. We now thus have two types of macros. UI macros (regular as before) and now the new so called data macros. It would not make sense for a table level macro to be able to display error messages to the screen. So any error logged goes into a table. There also a few new logging commands that let you write your own custom errors to that table . A brilliant and simple design here. Here what that error log table looks like:
(source: kallal.ca)
In a world of huge IDE’s, massive frame works and horrifying huge libraries of code requited to update a simple row in a table, I can say that data macros are most refreshing feature. They feel much like how the original dbaseII works. They are very simple, but deadly power full because they run at the table level.
For example, here is a data macro that will maintain inventorying totals a table. In this example I’m going to assume that master inventory records exist. And then we have an order details table. If a user edits any value in the orders table, we want the master table to automatic update the inventory levels.
So we have:
I have two tables
tblFruits: main data fruit inventory table
id (autonumber)
Fruit text
OnHand (number value of fruit in inventory)
tblFruitsOrder
id (autonumber)
Fruit_id (FK to tblFruts.ID)
QtyOrder (number of fruit to order)
This is simple test
So, we going to have a trigger in the tblFruitsOrder that will update
+ maintain inventory levels in tblFruits when the QtyOrder field is
edited or modified.
Here is what the macro looks like:
(source: kallal.ca)
Note how very simple the above is. Note that in the IDE if you click on a section of the code, then you get the old style macro type editing in which you can enter the values for the command (this is similar to pre 2010, but now the parameters and editing occurs in the code, not a panel that appears on the bottom of the screen in previous versions).
Here is another screen shot in which I playing with the ability to do a loop and call a subroutine.
(source: kallal.ca)
In the above we can use msgboxs etc. because this is not a table level macro. So the commands available are automatically restricted for you when you writing a table level macro as opposed to a regular macro. The terminology we adopted to distinguish the two types of macros are UI macros and data macros.
The above is about all I can speak about in pubic. However there is few more REALLY neat-o features about these macros that I simply can not yet talk about in public as I am still under NDA on those features. But there is more cool surprises to come here.
Here is a screen shot of the types of table triggers we have:
(source: kallal.ca)
More information on this new feature was posted today on the MS Access development team's blog and it definitely provides more information on the crucial question raised in the comments above.