Ideally avoid writing scripts that generate 100's of unrelated tables. Usually script generated tables have common features or relationships, and it might be better to make lists of them at the time of creation, that way you can manage what you have and where to look for them.
If the function class() returns a value that allows you to identify the objects you want to list, you can use a function like this one where I get a vector of the names of objects that have the class tbl
ClassFunc <- function(vec, ClassType) {
TYPES <- vector(mode = "character", length = length(vec))
for (i in seq_along(vec)) {
ClassVec <- class(get(vec[i]))
if (any(ClassVec == ClassType)) TYPES[i] <- vec[i]
}
return(TYPES[TYPES != ""])
}
ClassFunc(ls(), "tbl")
Of course, you can use ls() to search for objects whose name matches a pattern. That will work if you name all of your objects carefully.
generally the class of all the objects are dataframe ,etable and all the tables are like t1,t2,t3,t4.... but one thing is list of tables should be create as it is like
table_list <- list(t1,t2,t3,t4....) order of the tables should be consistent.
Lets say if will have many tables (etable,dataframes) assigned to (tb1, tb2,tb3,tb4,tb5.....tbn) and i want a list of those at the end. can we have any solution for this ..??