Home Information PDF Documents EULANDA Handbooks Training Book's corner Download Contact us Table of Contents About us

Glossary

Password needed Newsgroup

Remote Support system

Hide Records (SQL API)

Back | Level back

Connected data records can't be deleted because of the safety rules. If you don't want to delete the dependent data but determined data records suppressed for the searching, so you can change that with small changes.

When is the depending of data records meaningfully? For example if you need the statistic of the article stock of article but you don't want that statistic in a the new offer or order.

EULANDA® use for searching data Views, during the saving of changes direct in the physical table. 

You get this held back with that steps: During the searching all articles with a star at the beginning of there article number will be faded out. For this the available view will be derived and the name of the derived view will be stored in the SQL-Registry.

The steps in detail by the example article

That contribution is only for advanced user

  1. Changing the view name which were used for the article searching
  2. Add a new view
  3. EULANDA® restart
  4. Saves the changes in the SQL registry

1. Changing the view name which were used for the article searching

In the SQL registry under \ROOT\OBJECTS\Dataobjects\Eulanda.Artikel will be checked which name the searching view uses now. The name is saved in the field ViewTableName and is called MASTER_Artikel. Change this view table name into CUSTOM_ArtikelUngeloeschte.

2. Add a new View

That View will be derived but we name the new view CUSTOM_ArtikelUngeloeschte.

Hint

You should always pay attention with new views. Your own views must begin with CUSTOM_.  At the beginning you have to save the view as text file e.g. CUSTOM_ArtikelUngeloeschte.SQL.
During a update the structure (in that case article structure) could be changed. In this case the SQL server shifts the result fields. You can protect your system by a new learning the view from the SQL server. You can use the same command but instead of CREATE you use ALTER.

The view CUSTOM_ArtikelUngeloeschte will be created with the following command in the SQL-Designer, you find it in the system managment.

CREATE VIEW CUSTOM_ArtikelUngeloeschte
AS
SELECT * FROM MASTER_Artikel WHERE NOT LEFT(ArtNummer,1)='*'

After that, you start the SQL-Script with Strg+E. If the input was correct you could see a success message in the text output range.

If your user rights are not sufficient for these changes, you could see a error message in the output range. If you have that problem, you have to log in with the administration account in the data menu of the SQL designer with the function Databaseconnection.

3. EULANDA® restart

Restart EULANDA® after the changing

If you call a article and change it by adding a star at the first place of the article number and so the article won't be found in the future.

4. Saving the SQL registry changing

Please consider that the changes of the SQL registry by an update will be overwrite. You have to save your changes only with the export function of the changed registry key (right mouse button) and save these changes in a own file. After an update you only need to import the files.

Hint:

If you want show the hidden articles, you have to change the ViewTableName in the SQL registry again. You have to change the name to the original value in MASTER_Article and restart the EULANDA®.