This small dataset (as it is coming from MS-Access) you want to do some reporting on. You did not mention you environment/tools of SAS you are using. Also nothing on a support staff, - Eguide is nice in click/for some results - A BI/Di team could do the coding work for you. Reporting in SAS is done for example with Base SAS(R) 9.4 Procedures Guide (Proc report) No need to prepare counts as a dataset tabel in advance before presenting it. It is done all within that procedure. ... View more

The proc datasets,  with 9.4 proc delete is back, is the best way to clean up SAS managed data/content. (ODS and OMI to be added). You could run this SAS code by a SAS batch-job using a batch file. Keep it simple (KISS) the one (owner/process) creating the rubbish should also do the cleanup. In excptions a Garbage clean service. The issue you are possible running into is locking. Locking is well known from databases.  It first implementation was on mulituser OS. When someone has locked a record somebody else cannot use that record in the same way.  To overcome the dealocks for updating you can tell just doing reads. Windows is now multiuser and can do locking. The Original DOS 2.1 single user single machine was missing that.   Even weird behavior can oocur like: Configuring opportunistic locking in Windows Unix has been designed for multiuser but is mostly missing a multiuser implementation. Phones - routers etc a single proces person. Old guy Mainframe was the most strict on this (disp=..) .   That should be background knowledge. SAS is running on top of and OS and has to follow what is delivered by that. Filelocks are possible. Setting a directory for read-only will have the access for read-only no updates (including deletes). You cannot change that be defining an other libname it will reuse the old ones (trying to disconenct/connect first).    Seen you last note accessing the server, you are moving form old SAS base/foundation to using BI/DI with Eguide. With Eguide the SASuser is closed (read-only) no garbage will be created anymore. Advice: - Do a cleanup for one time - go for you users to implement and support something that is workable for temp/permanent datasets ... View more

And scott went on.... https://communities.sas.com/message/178205#178205 ... View more

Ok Bill,  metadata is very confusing as there are more ways it is being used.  The global meaning of metadata is that is describing the data you are using. Call it a Data Dictionary. SAS datasets and DBMS tables commonly already having a dictionary off that. Open up a table and you see all variables types labels. As long a you are using to do work an those tables that is sufficient. The libraries (pathname/schema) you are using, you could setup them in a autoexec eg project source. With this approach nothing of libraries or tables is needed in the SAS metadatabase. Chris Hemedinger made some nice postings in hsi blog on that You asked for it: the Autoexec process flow - The SAS Dummy The SAS metadatabase is that thing seeing by SMC or by Eguide as "SASapp". What you see by Eguide is a part below SASapp called the Workspace Server (WS). Your admin  should be able to find that in SMC and the configuration files of SAS at OS level.  When you are using DI studio, Information maps or more of the approach where the libraries tables are needed in the SAS metdatabase these tables and libraries need to be registered there. In this approach it is common to do lifecyclemanagement while developping something. As long you are only the Anlyst working with data you could go for the first mentioned easy approach just working with Eguide and not bothering too much about the SAS metdataserver. ... View more

Please Elaborate... Eguide can be used to register data to metadata (when autorized) A lot of data (work) you won't like to be registered. ... View more

The construction with conditions and using lag in it is confusing The LAG function is a logical queue construct pushing the current value in and getting the oldest out of it. It is not the same as a retain. SAS(R) 9.4 Functions and CALL Routines: Reference (LAG) At the first time " mylabel=1+lag1(mylabel); " is called (_n_ =2)  it will push a missing in the que as mylabel for that observation has not been defined. It is exactly working as has been described.  ... View more

mikesatriavo,  Did you read teh reference fugue had given? SAS(R) 9.4 Language Reference: Concepts (Numeric Precision in SAS Software). The title here is wrong it is not SAS related as it applies to all kind of floating processing (flops). It is IEE standard. This is something as fundamental to calculations for a very very long time. Floatings are by definition not precise.           Compressing is just a method for saving dasd space doesn't have any effect to numeric precision (length max=8 has). The remark on handling as character is also sensible. - The average on female=1 male=2 makes no sense as it is a classification. - IBAN numbers are even no numbers.   The way of limiting to numbers at sme areas is going back to the old hollerith age having visible 10 columns. Working on a DBMS with those many more datatypes, there is a new language added in SAS (9.3 last uypdates, 9.4) "PROC DS2" http://support.sas.com/documentation/cdl/en/proc/64787/HTML/default/viewer.htm#n08hc15x330v75n1vjw9rzlbhe84.htm ... View more

sandy,  Your problem is now well described.  SASUSER and the personal data storage. The batch file has the issue you have to know all users and have all acessrigts there. They probably not running under "ussasadmin"but under their own key. So  C:\Documents and Settings\ussasadmin\My Documents\My SAS Files\9.1\*.sas7bdat  will not work. SASuser is meant to be personal  connected to the %USERPROFILE% of windows. A more adavanced reference is used. Trying to force people not using their "My documents" etc while Microsoft is pushing them direction is a losing game. The better approach would be a setting they are not tempted that easy storing data in SASUSER.   With Eguide usage this SASuser location is set often read-only within SAS by default.  You are describing a DMS approach (SAS base). The storing of data with 1-level names is a easy approach of coding and can be influenced.      The issue of the sasuser usage can be solved different. SAS(R) 9.3 Companion for Windows (user= system option). You could set it to the same as WORK. But by default this location is %TEMP% also bound to be to the personal key. There must be a location for user-modifications in the config.sas at your installation. ... View more