LISTSERV at the University of Georgia
Menubar Imagemap
Home Browse Manage Request Manuals Register
Sort by authorSort by posting dateSort by topic[Separator]Chronological orderMost recent first[Separator]Show authorHide author[Separator]Back to main SAS-L pageJoin or leave SAS-L (or change settings)Search
SAS-L archives – January 2011, week 2

  1. Re: Maximum Size for Character Variables? (168 lines)
  2. Re: partitioning a variable (108 lines)
  3. Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (45 lines)
  4. Re: Least and most helpful SAS error message (45 lines)
  5. Re: RTF Output (66 lines)
  6. Re: Maximum Size for Character Variables? (342 lines)
  7. Re: Maximum Size for Character Variables? (142 lines)
  8. Re: Maximum Size for Character Variables? (135 lines)
  9. Re: Maximum Size for Character Variables? (153 lines)
  10. Re: Logistic Regression Intercept Pr>Chisq (51 lines)
  11. Re: Logistic Regression Intercept Pr>Chisq (40 lines)
  12. Re: markov transition model with binary response (42 lines)
  13. Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (83 lines)
  14. Re: Maximum Size for Character Variables? (361 lines)
  15. Re: markov transition model with binary response (50 lines)
  16. Re: Automatic Sorting (50 lines)
  17. Re: Maximum Size for Character Variables? (374 lines)
  18. Re: Logistic Regression Intercept Pr>Chisq (73 lines)
  19. Re: Maximum Size for Character Variables? (412 lines)
  20. Re: SAS-L Digest - 8 Jan 2011 - Special issue (#2011-34) (126 lines)
  21. Re: Logistic Regression Intercept Pr>Chisq (30 lines)
  22. Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (88 lines)
  23. Re: markov transition model with binary response (59 lines)
  24. Things we'd like to see in SAS - What I would like to see in the next SAS version (102 lines)
  25. Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (104 lines)
  26. Re: Things we'd like to see in SAS - What I would like to see in the next SAS version (152 lines)
  27. Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (95 lines)
  28. Re: Things we'd like to see in SAS - What I would like to see in the next SAS version (32 lines)
  29. Re: Things we'd like to see in SAS - What I would like to see in the next SAS version (49 lines)
  30. Re: Things we'd like to see in SAS - What I would like to see in the next SAS version (57 lines)
  31. Re: Things we'd like to see in SAS - What I would like to see in the next SAS version (73 lines)
  32. Re: markov transition model with binary response (76 lines)
  33. DDE, graphics, and MS Word..... (121 lines)
  34. Re: DDE, graphics, and MS Word..... (141 lines)
  35. Re: DDE, graphics, and MS Word..... (150 lines)
  36. Re: Maximum Size for Character Variables? (114 lines)
  37. ods graphics - sgpanel (85 lines)
  38. Re: ods graphics - sgpanel (101 lines)
  39. Re: ods graphics - sgpanel (131 lines)
  40. Re: ods graphics - sgpanel (154 lines)
  41. Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (56 lines)
  42. Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (93 lines)
  43. Re: Maximum Size for Character Variables? (653 lines)
  44. Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (96 lines)
  45. Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (28 lines)
  46. Re: DDE, graphics, and MS Word..... (13 lines)
  47. Re: partitioning a variable (14 lines)
  48. Re: ods graphics - sgpanel (53 lines)
  49. Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (12 lines)
  50. how to output the median in proc univiariate or proc means (50 lines)
  51. Re: how to output the median in proc univiariate or proc means (72 lines)
  52. Creating subset of data and calculate weighted means for depth (54 lines)
  53. Re: how to output the median in proc univiariate or proc means (79 lines)
  54. write a book on SAS programming (for SAS programmers, not just for SAS users ) (116 lines)
  55. Re: Creating subset of data and calculate weighted means for depth (99 lines)
  56. Re: write a book on SAS programming (for SAS programmers, not just for SAS users ) (141 lines)
  57. Re: write a book on SAS programming (for SAS programmers, not just for SAS users ) (154 lines)
  58. Re: how to output the median in proc univiariate or proc means (66 lines)
  59. Re: Creating subset of data and calculate weighted means for depth (152 lines)
  60. Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (63 lines)
  61. Re: Creating subset of data and calculate weighted means for depth (177 lines)
  62. command line parameters for EG? (22 lines)
  63. Re: Creating subset of data and calculate weighted means for depth (180 lines)
  64. algorithm for nice ticmark values (19 lines)
  65. Re: algorithm for nice ticmark values (32 lines)
  66. Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (97 lines)
  67. Re: algorithm for nice ticmark values (39 lines)
  68. Re: algorithm for nice ticmark values (30 lines)
  69. Re: algorithm for nice ticmark values (65 lines)
  70. Re: write a book on SAS programming (for SAS programmers, not just for SAS users ) (147 lines)
  71. Re: write a book on SAS programming (for SAS programmers, not just for SAS users ) (204 lines)
  72. Re: Creating subset of data and calculate weighted means for depth (1586 lines)
  73. Determine if a dataset was last modified after a series of other data sets. (25 lines)
  74. Re: Determine if a dataset was last modified after a series of other data sets. (46 lines)
  75. Mathematical function (107 lines)
  76. Re: Mathematical function (120 lines)
  77. Re: Creating subset of data and calculate weighted means for depth (1617 lines)
  78. Re: Creating subset of data and calculate weighted means for depth (1615 lines)
  79. Re: Creating subset of data and calculate weighted means for depth (1650 lines)
  80. Re: Creating subset of data and calculate weighted means for depth (1678 lines)
  81. Re: Creating subset of data and calculate weighted means for depth (1750 lines)
  82. Re: help with matching without replacement (67 lines)
  83. Re: Creating subset of data and calculate weighted means for depth (1824 lines)
  84. Re: Creating subset of data and calculate weighted means for depth (1836 lines)
  85. Re: Creating subset of data and calculate weighted means for depth (1784 lines)
  86. Re: Creating subset of data and calculate weighted means for depth (3714 lines)
  87. Re: Creating subset of data and calculate weighted means for depth (29 lines)
  88. Re: Creating subset of data and calculate weighted means for depth (1815 lines)
  89. Re: Creating subset of data and calculate weighted means for depth (62 lines)
  90. Any one familiar with hardware needed for Windows Server (19 lines)
  91. Re: Creating subset of data and calculate weighted means for depth (1798 lines)
  92. Re: Creating subset of data and calculate weighted means for depth (81 lines)
  93. Re: SAS Unix (344 lines)
  94. Re: SAS Unix (355 lines)
  95. Re: SAS Unix (368 lines)
  96. Re: SAS Unix (456 lines)
  97. Re: SAS Unix (463 lines)
  98. Re: SAS Unix (511 lines)
  99. Re: SAS Unix (539 lines)
  100. Re: Creating subset of data and calculate weighted means for depth (134 lines)
  101. Re: SAS Unix (265 lines)
  102. Re: Creating subset of data and calculate weighted means for depth (141 lines)
  103. Re: write a book on SAS programming (for SAS programmers, not just for SAS users ) (150 lines)
  104. What procedure should I use for p-value (51 lines)
  105. Re: Any one familiar with hardware needed for Windows Server (55 lines)
  106. Re: Creating subset of data and calculate weighted means for depth (183 lines)
  107. Re: how to output the median in proc univiariate or proc means (77 lines)
  108. Re: Creating subset of data and calculate weighted means for depth (179 lines)
  109. Re: Creating subset of data and calculate weighted means for depth (23 lines)
  110. Re: write a book on SAS programming (for SAS programmers, not just for SAS users ) (180 lines)
  111. Re: Creating subset of data and calculate weighted means for depth (41 lines)
  112. Re: write a book on SAS programming (for SAS programmers, not just for SAS users ) (210 lines)
  113. Re: write a book on SAS programming (for SAS programmers, not just for SAS users ) (51 lines)
  114. Re: write a book on SAS programming (for SAS programmers, not just for SAS users ) (214 lines)
  115. Re: write a book on SAS programming (for SAS programmers, not just for SAS users ) (223 lines)
  116. Re: DDE, graphics, and MS Word..... (37 lines)
  117. Re: write a book on SAS programming (for SAS programmers, not just for SAS users ) (307 lines)
  118. Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (231 lines)
  119. Re: DDE, graphics, and MS Word..... (69 lines)
  120. <No subject> (443 lines)
  121. Re: Creating subset of data and calculate weighted means for depth (1846 lines)
  122. Problem with 3 way merge (81 lines)
  123. Re: Creating subset of data and calculate weighted means for depth (1640 lines)
  124. Re: Any one familiar with hardware needed for Windows Server (29 lines)
  125. Re: markov transition model with binary response (88 lines)
  126. Re: write a book on SAS programming (for SAS programmers, not just for SAS users ) (30 lines)
  127. Re: DDE, graphics, and MS Word..... (16 lines)
  128. Re: write a book on SAS programming (for SAS programmers, not just for SAS users ) (58 lines)
  129. Re: write a book on SAS programming (for SAS programmers, not just for SAS users ) (278 lines)
  130. Re: write a book on SAS programming (for SAS programmers, not just for SAS users ) (257 lines)
  131. Re: write a book on SAS programming (for SAS programmers, not just for SAS users ) (293 lines)
  132. SAS/IML : using R package (56 lines)
  133. Re: SAS/IML : using R package (84 lines)
  134. Re: write a book on SAS programming (for SAS programmers, not just for SAS users ) (44 lines)
  135. Re: SAS/IML : using R package (67 lines)
  136. Re: SAS/IML : using R package (23 lines)
  137. Re: SAS/IML : using R package (25 lines)
  138. Re: markov transition model with binary response (82 lines)
  139. Re: SAS/IML : using R package (63 lines)
  140. Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (35 lines)
  141. Re: markov transition model with binary response (105 lines)
  142. Large dataset - deleting rows (28 lines)
  143. RES: markov transition model with binary response (122 lines)
  144. Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (23 lines)
  145. Re: algorithm for nice ticmark values (30 lines)
  146. Re: markov transition model with binary response (137 lines)
  147. Re: Fun With SAS - My Vote for Oddest SAS Programming Language "Feature" (42 lines)
  148. Copying catalog entries without overwriting (19 lines)
  149. Re: What procedure should I use for p-value (78 lines)
  150. SAS / JMP 8.0.2 (15 lines)
  151. Re: SAS / JMP 8.0.2 (28 lines)
  152. Re: SAS / JMP 8.0.2 (36 lines)
  153. Re: Problem with 3 way merge (20 lines)
  154. Re: SAS / JMP 8.0.2 (43 lines)
  155. Re: SAS / JMP 8.0.2 (48 lines)
  156. Re: Problem with 3 way merge (29 lines)
  157. Re: Problem with 3 way merge (45 lines)
  158. Identify ties for values of variables (21 lines)
  159. Re: Identify ties for values of variables (29 lines)
  160. Re: Problem with 3 way merge (201 lines)
  161. Continuous NUmbers (13 lines)
  162. Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (92 lines)
  163. Proc Export difference between dbms=xls and dbms=excel (35 lines)
  164. Re: Large dataset - deleting rows (35 lines)
  165. Re: Identify ties for values of variables (43 lines)
  166. Re: SAS / JMP 8.0.2 (28 lines)
  167. Re: Continuous NUmbers (24 lines)
  168. Count of Visits/Patients more Efficient (83 lines)
  169. Re: Continuous NUmbers (45 lines)
  170. Re: Identify ties for values of variables (81 lines)
  171. Re: Identify ties for values of variables (103 lines)
  172. Re: Count of Visits/Patients more Efficient (115 lines)
  173. Re: Continuous NUmbers (53 lines)
  174. Re: Identify ties for values of variables (143 lines)
  175. Re: Identify ties for values of variables (122 lines)
  176. Slice option in PROC SURVEYLOGISTIC (65 lines)
  177. Re: Identify ties for values of variables (163 lines)
  178. need helps in data analysis (131 lines)
  179. Re: Identify ties for values of variables (62 lines)
  180. Re: Proc Export difference between dbms=xls and dbms=excel (74 lines)
  181. Re: Count of Visits/Patients more Efficient (7 lines)
  182. Re: need helps in data analysis (148 lines)
  183. Re: Proc Export difference between dbms=xls and dbms=excel (41 lines)
  184. Re: need helps in data analysis (175 lines)
  185. 3-way combine (129 lines)
  186. Re: 3-way combine (31 lines)
  187. Re: Proc Export difference between dbms=xls and dbms=excel (19 lines)
  188. Re: 3-way combine (42 lines)
  189. stack datasets together (20 lines)
  190. Re: stack datasets together (35 lines)
  191. Re: markov transition model with binary response (163 lines)
  192. Re: stack datasets together (35 lines)
  193. Re: stack datasets together (43 lines)
  194. Re: stack datasets together (43 lines)
  195. CleveSUG Winter Meeting 2/14/2011 (20 lines)
  196. Re: Proc Export difference between dbms=xls and dbms=excel (54 lines)
  197. Re: write a book on SAS programming (for SAS programmers, not just for SAS users ) (304 lines)
  198. how to drop no of variables in datstep? (18 lines)
  199. Re: Slice option in PROC SURVEYLOGISTIC (98 lines)
  200. Re: how to drop no of variables in datstep? (49 lines)
  201. Re: Proc Export difference between dbms=xls and dbms=excel (64 lines)
  202. Re: how to drop no of variables in datstep? (108 lines)
  203. Can PROC PRINT create MISSING VALUES? (21 lines)
  204. Error Message -= A lock in not available (88685 lines)
  205. Re: write a book on SAS programming (for SAS programmers, not just for SAS users ) (359 lines)
  206. Re: Can PROC PRINT create MISSING VALUES? (35 lines)
  207. SAS job opening in Toronto (51 lines)
  208. Re: Error Message -= A lock in not available (13 lines)
  209. Re: Copying catalog entries without overwriting (33 lines)
  210. New SAS-L World Record (30 lines)
  211. Transpose by SQL (14 lines)
  212. Re: Can PROC PRINT create MISSING VALUES? (59 lines)
  213. Re: Transpose by SQL (44 lines)
  214. .xpt to SAS (91 lines)
  215. Re: .xpt to SAS (109 lines)
  216. Re: Transpose by SQL (27 lines)
  217. Re: New SAS-L World Record (45 lines)
  218. Re: SAS/IML : using R package (99 lines)
  219. Re: New SAS-L World Record (40 lines)
  220. Re: Transpose by SQL (108 lines)
  221. Re: Continuous NUmbers (36 lines)
  222. Keyboard Macros (11 lines)
  223. Re: Transpose by SQL (130 lines)
  224. Re: Transpose by SQL (144 lines)
  225. delete (17 lines)
  226. Re: Keyboard Macros (23 lines)
  227. Re: delete (25 lines)
  228. Re: Keyboard Macros (9 lines)
  229. Re: Transpose by SQL (66 lines)
  230. Create two vars from one var (49 lines)
  231. Re: Create two vars from one var (69 lines)
  232. Re: Can PROC PRINT create MISSING VALUES? (84 lines)
  233. Re: Any one familiar with hardware needed for Windows Server (70 lines)
  234. Re: Keyboard Macros (39 lines)
  235. Re: OT: Chance to Make SAS-L History: Did You Know That... (122 lines)
  236. Easy macro comparison (32 lines)
  237. Re: Easy macro comparison (72 lines)
  238. Re: Easy macro comparison (94 lines)
  239. Re: Easy macro comparison (57 lines)
  240. Re: Easy macro comparison (119 lines)
  241. Re: Any one familiar with hardware needed for Windows Server (45 lines)
  242. Re: Any one familiar with hardware needed for Windows Server (56 lines)
  243. Re: delete (50 lines)
  244. Re: Error Message -= A lock in not available (71 lines)
  245. Enterprise BI (22 lines)
  246. Re: Error Message -= A lock in not available (3214 lines)
  247. Re: Error Message -= A lock in not available (21 lines)
  248. Data step code for matrix inversion (211 lines)
  249. Re: Determine if a dataset was last modified after a series of other data sets. (27 lines)
  250. Re: Identify ties for values of variables (27 lines)
  251. Files in a directory (without X) (38 lines)
  252. RES: Re: Error Message -= A lock in not available (75 lines)
  253. Re: Files in a directory (without X) (48 lines)
  254. Re: SAS Unix (393 lines)
  255. Re: Files in a directory (without X) (63 lines)
  256. NESUG or other RUG question re Hand On Workshops (20 lines)
  257. Re: Files in a directory (without X) (71 lines)
  258. Re: Files in a directory (without X) (75 lines)
  259. AIC and P-seudo R2 for TOBIT Model (54 lines)
  260. Re: SAS Unix (477 lines)
  261. Re: SAS Unix (553 lines)
  262. Error Message in SAS (29 lines)
  263. Re: NESUG or other RUG question re Hand On Workshops (34 lines)
  264. Re: Files in a directory (without X) (118 lines)
  265. Re: Files in a directory (without X) (95 lines)
  266. Re: Files in a directory (without X) (133 lines)
  267. Re: Files in a directory (without X) (52 lines)
  268. Re: Files in a directory (without X) (151 lines)
  269. Hash Case/Control Matching (25 lines)
  270. Hash Case/Control Matching (42 lines)
  271. SAS unix (35 lines)
  272. Re: Hash Case/Control Matching (51 lines)
  273. Re: Files in a directory (without X) (282 lines)
  274. Re: NESUG or other RUG question re Hand On Workshops (65 lines)
  275. Re: Enterprise BI (40 lines)
  276. Re: AIC and P-seudo R2 for TOBIT Model (130 lines)
  277. Re: Frustration With SAS - My Vote for most poorly implemented Programming Language "Feature" (113 lines)
  278. Re: Enterprise BI (60 lines)
  279. Re: Enterprise BI (75 lines)
  280. Re: New SAS-L World Record (54 lines)
  281. Predicted mean square error quintic spline (37 lines)
  282. RES: AIC and P-seudo R2 for TOBIT Model (150 lines)
  283. Re: Error Message in SAS (49 lines)
  284. frequency marching (16 lines)
  285. Re: New SAS-L World Record (98 lines)
  286. please recommend books for advanced certification exam (22 lines)
  287. Re: frequency marching (35 lines)
  288. Recursive lookup (53 lines)
  289. Re: frequency marching (34 lines)
  290. Version 9.2 macro change (If then else) (29 lines)
  291. Re: Version 9.2 macro change (If then else) (41 lines)
  292. Re: New SAS-L World Record (84 lines)
  293. Re: Recursive lookup (78 lines)
  294. Re: New SAS-L World Record (55 lines)
  295. Re: Error Message in SAS (170 lines)
  296. Re: Recursive lookup (96 lines)
  297. QLIM Output Error (70 lines)
  298. data entry? (34 lines)
  299. Re: RES: AIC and P-seudo R2 for TOBIT Model (176 lines)
  300. Re: data entry? (65 lines)
  301. Training on SAS using your home PC (22 lines)
  302. Re: QLIM Output Error (137 lines)
  303. Re: Training on SAS using your home PC (34 lines)
  304. Re: Training on SAS using your home PC (73 lines)
  305. Re: Recursive lookup (161 lines)
  306. Re: Training on SAS using your home PC (60 lines)
  307. Re: Training on SAS using your home PC (34 lines)
  308. Re: Training on SAS using your home PC (52 lines)
  309. Re: Training on SAS using your home PC (56 lines)
  310. Re: Training on SAS using your home PC (70 lines)
  311. Re: Recursive lookup (168 lines)
  312. Re: Training on SAS using your home PC (89 lines)
  313. Re-ordering data (136 lines)
  314. Re: Training on SAS using your home PC (107 lines)
  315. Re: Re-ordering data (148 lines)
  316. Re: Re-ordering data (161 lines)
  317. Re: how to drop no of variables in datstep? (26 lines)
  318. Proc Report PDF (38 lines)
  319. Re: Version 9.2 macro change (If then else) (55 lines)
  320. RES: RES: AIC and P-seudo R2 for TOBIT Model (59 lines)
  321. Merge with same var name in both datasets (55 lines)
  322. Re: write a book on SAS programming (for SAS programmers, not just for SAS users ) (57 lines)
  323. Re: Version 9.2 macro change (If then else) (75 lines)
  324. Re: Files in a directory (without X) (76 lines)
  325. Re: Merge with same var name in both datasets (76 lines)
  326. Re: Merge with same var name in both datasets (95 lines)
  327. Re: Merge with same var name in both datasets (15 lines)
  328. Re: Merge with same var name in both datasets (36 lines)
  329. Mutlinomial Logit to Binomial Logit.. (52 lines)
  330. Re: Merge with same var name in both datasets (36 lines)
  331. Re: NESUG or other RUG question re Hand On Workshops (68 lines)
  332. Re: Merge with same var name in both datasets (60 lines)
  333. Re: Mutlinomial Logit to Binomial Logit.. (81 lines)
  334. Re: Merge with same var name in both datasets (79 lines)
  335. Re: NESUG or other RUG question re Hand On Workshops (92 lines)
  336. OT: Friday Humor (21 lines)
  337. Re: NESUG or other RUG question re Hand On Workshops (54 lines)
  338. Mutlinomial Logit to Binomial Logit.. (107 lines)
  339. Re: NESUG or other RUG question re Hand On Workshops (77 lines)
  340. Exporting SAS files as Oracle files (16 lines)
  341. Re: Exporting SAS files as Oracle files (33 lines)
  342. Re: Exporting SAS files as Oracle files (46 lines)
  343. Can someone with 9.1 or earlier test this code? (28 lines)
  344. Re: Can someone with 9.1 or earlier test this code? (70 lines)
  345. Re: Can someone with 9.1 or earlier test this code? (39 lines)
  346. Re: Can someone with 9.1 or earlier test this code? (56 lines)
  347. Re: Can someone with 9.1 or earlier test this code? (66 lines)
  348. Re: Exporting SAS files as Oracle files (36 lines)
  349. Re: Can someone with 9.1 or earlier test this code? (80 lines)
  350. Re: Can someone with 9.1 or earlier test this code? (65 lines)
  351. Re: Can someone with 9.1 or earlier test this code? (24 lines)
  352. UK US Pricing for SAS genetics (18 lines)
  353. SAS IntrNet: %do and the corresponding %end match (149 lines)
  354. Re: Can someone with 9.1 or earlier test this code? (123 lines)
  355. Re: Error Message in SAS (289 lines)
  356. Re: Can someone with 9.1 or earlier test this code? (146 lines)
  357. Re: SAS IntrNet: %do and the corresponding %end match (180 lines)
  358. Re: SAS IntrNet: %do and the corresponding %end match (38 lines)
  359. Re: Can someone with 9.1 or earlier test this code? (112 lines)
  360. Re: Exporting SAS files as Oracle files (67 lines)
  361. Re: SAS IntrNet: %do and the corresponding %end match (71 lines)
  362. Re: SAS IntrNet: %do and the corresponding %end match (86 lines)
  363. Find Records in a Cluster by Date (59 lines)
  364. Excel tagsets - dropped zeros and numbers as text. (70 lines)
  365. Re: Excel tagsets - dropped zeros and numbers as text. (83 lines)
  366. Forecasting data based on linkages (64 lines)
  367. Re: Find Records in a Cluster by Date (97 lines)
  368. Re: Training on SAS using your home PC (44 lines)
  369. Re: Excel tagsets - dropped zeros and numbers as text. (87 lines)
  370. Re: Excel tagsets - dropped zeros and numbers as text. (105 lines)
  371. Re: Forecasting data based on linkages (23 lines)
  372. Re: Find Records in a Cluster by Date (75 lines)
  373. Re: Find Records in a Cluster by Date (104 lines)
  374. Re: Find Records in a Cluster by Date (119 lines)
  375. Re: Find Records in a Cluster by Date (132 lines)
  376. Re: Excel tagsets - dropped zeros and numbers as text. (286 lines)
  377. Re: Excel tagsets - dropped zeros and numbers as text. (304 lines)
  378. PROC REPORT - Across variables and cell widths in HTML output (47 lines)
  379. Re: Find Records in a Cluster by Date (194 lines)
  380. Re: PROC REPORT - Across variables and cell widths in HTML output (76 lines)
  381. Re: PROC REPORT - Across variables and cell widths in HTML output (89 lines)
  382. Re: Excel tagsets - dropped zeros and numbers as text. (651 lines)
  383. Re: Can someone with 9.1 or earlier test this code? (79 lines)
  384. Re: Can someone with 9.1 or earlier test this code? (99 lines)
  385. Re: Can someone with 9.1 or earlier test this code? (21 lines)
Back to the main SAS-L page