By no means I am an expert, but responding to let you know that Sesame can handle document management system very well. I know because I have one and that handles various documents, .pdf, doc, docx, jpg, xls, etc., for all my more than three thousands active clients. I also have document management system in my personal organizer system.

In my system, Documents is a subform in tableview, meaning it is a subdatabase. A document can be opened up using Asynchshell ( ) command on element entry event in one of the tableview elements.  Sesame does not have the field that could display pdf file but it will be displayed in pdf reader or Adobe Acrobat or any other program associated with pdf file in your pc. The same is applicable to other documents file such as doc or xls. The document can be scanned in directly (I use TwainSave program) or picked up from email or anywhere in your file manager of PC. Description that you enter will be used to locate it by search parameters and unique filename is generated by the programming. My documents are in the cloud and they automatically synch to network pc at home or office. The documents are available to me also on the road using Teamviewer with my cellphone or tablet. 

Since you are testing the program, I thought it is not inappropriate to point out the awesome power of Sesame that a non-programmer like me can harness!! Once you will start using the program and put a few codes here and there, you will start feeling confident and see what more you can do with Sesame. Your greatest asset while learning will be this forum. Just place a query here and you will be surprised that how many people are out there, eager to help you. Good Luck.

Here's attachment 2. The preview mode on my screen looks like this:

Tree view versus button view menus?

Yes, the default menu changed between versions 2.0 and 2.5. You can, however, switch between them and use whichever you prefer. The button menu is simpler and initially easier to use. The tree menu is more complex and powerful. There are entries in the file sesame.ini that control much of the user interface:

https://www.lantica.com/support/kb/article/000217

Since you are making Document database, you probably will have to work with scanner for atleast some of the documents. Following thread will get you thinking...

http://lantica.com/Forum4/cgi-bin/yabb2/YaBB.pl?num=1302811064/5#5

Sesame can store the document internally (by translation in base-64),  but I strongly recommend that you simply store the path to the document. Storing it internally is very space consumming and doesn't really have any benefit other than making it easier to move the application from one computer to another, which can otherwise be easily programmed.

Quote:

Mark, just wondering how that is done? Do we need to use converter and encoder?  I have been using  storing the path method and avoid having a bloated application. But still wondering, how is it stored internally? I am wondering if anyone of the users is using the base-64 internal storage method?

@Bharat_Naik
I plan to have 1-9 documents within one dataset.
Also i plan to store all documents in a subfolder of my database files and use the "document link feature"

StreifLicht,

I do not want to confuse and complicate the process you are following, however I thought I would give you something else to think about once you are comfortable with Sesame.

Very soon you will learn that Sesame is not only easy to use but super powerful and will allow you to do most anything you desire.

I have a similar application to what you describe. I store documents on a shared drive and have the sesame application name the document and then place it on that drive. One of the problems my users had was on some records not all the documents were present so they never knew when pressing a button to view if something was there.

Below is a small snippet of code as an example that when entering a client record it looks to see what docs are available, turns a checkbox green or red and makes a command button either visible or not based on if a document is present.

This way the user knows instantly what is available.

I am not sure of the type of documents you are dealing with, however if they are PDf's the people on this board helped me find a method that automatically adds docs to existing types of PDF's so if you add more docs of the same specific type (say additional letters they sent) it just appends the existing pdf.

When and if you need any of these features just ask and we can post up the sbasic snippits.   

Enjoy Sesame its a great product!

Subroutine TA_docYN() // checks and updates presence of docs
// This checks to see if the completed employee docs form is in the directory and puts a check mark in field element YNEP      
iF      FileExists("s:\EP\" +TA_id+"EP.pdf") // needs to be changed based on working directory
     
     {
                 YNEP = 1
           RGBColor(YNEP,-1,-1,-1,0,255,0)
           Visibility(ButtonVEP, 1)      
           Forceredraw()
           //writeln("Green")      
           
     

     }
     else
     {
     

           YNEP = 0
           RGBColor(YNEP,-1,-1,-1,255,0,0)
           Visibility(ButtonVEP, 0)
           Forceredraw()
           //writeln("Red")            
     }



// This checks to see if the correspondence docs form is in the directory and puts a check mark in field element YNCOR      
iF      FileExists("s:\COR\" +TA_id+"COR.pdf") // needs to be changed based on working directory
     
     {
     
     
           YNCOR = 1
           RGBColor(YNCOR,-1,-1,-1,0,255,0)
           Visibility(ButtonVCOR, 1)      
           Forceredraw()
           //writeln("Green")      
           
     

     }
     else
     {
     

           YNCOR = 0
           RGBColor(YNCOR,-1,-1,-1,255,0,0)
           Visibility(ButtonVCOR, 0)
           Forceredraw()
           //writeln("Red")            
     }


End Subroutine

If I understand correctly you want to press a button and make a document part of the record.

What I do is to pop up a selection box for a user to select the type of document they are wanting to attach to the record.

I then have Sesame present a dialog box to select the file. (mine opens in c:\attach)

I then have sbasic rename the file so it is associated to the record and then place the file in the proper directory for access by any user who is allowed.

The code I presented earlier in this thread is then used to notify the user in the future if the record they enter has available documents and the view button is then used to instantly access the document.

I know my code is not the best written and there are so many different ways to accomplish the same goals with sesame, however the code below can be used as an example of how to do this and get you thinking and going in the correct direction.

I added comments to try and help you understand what is going on in the code.

// Declaring my variables
var Vresult as string
Var m as int
Var n as int
Var s as int
Var D as int
var Vrname as string
var Vshow as string


var vResult1 as string
var vChoices as string
var vDocType as string

var vDir as string
var vDirNfile as string
var vview as string


     vDocType = ""
// These are the choices the users will see in the pop up to select type of doccument
     vChoices = "Script;" +
     "Medical Documentation;" +
     "Insurance Docs;" +
     "Hst Recieved Doc;" +
     "HST Sent Back Doc;" +
     "HST Questionnaire;" +
     "HST Study;" +
     "HST Study 2;" +
     "HST Study 3;" +
     "Interp 1;" +
     "Interp 2;" +
     "Interp 3;" +
     "Signed Super Bill 1;" +
     "Signed Super Bill 2;" +
     "Signed Super Bill 3"

//  this is setting where to display the pop up on my screen In this example I want it to pop up near my element called status
     PopupSelectPosition(4, @XPos(status), @YPos(status))

// This is running the pop up for the document type
     vResult1 = @PopupChoiceList(vChoices, "Select A Document Type to upload")

     if vResult1 = ""

     {
           @Msgbox("","No Document type Selected","")


     }
     
else

     {


           vDocType = vResult1
           //Writeln(vResult1)
     
                 if vDocType = "Script"

                       {
                             vDocType = "script"
                             vDir = "sesame\script\done\"
                       }

     else
                       
                 if vDocType = "Signed Super Bill 1"

                       {
                             vDocType = "sb1"
                             vDir = "sb1\"
                       }

     else

                       

                 if vDocType = "Signed Super Bill 2"      

                       {
                             vDocType = "sb2"
                             vDir = "SB2\"
                       }

     else
     
                 if vDocType = "Signed Super Bill 3"
     
                       {
                             vDocType = "sb3"
                             vDir = "SB3\"
                       }

     else
     
                 if vDocType = "Medical Documentation"

                       {
                             vDocType = "MedDoc"
                             vDir = "MedDoc\"
                       }

     else

     
                 if vDocType = "Insurance Docs"

                       {
                             vDocType = "InsDoc"
                             vDir = "InsDoc\"
                       }

     else
     

                 if vDocType = "HST STudy"
                 
                       {

                             vDocType = "HSTStudy"
                             vDir = "HSTStudy\"
                       }
     else
     

                 if vDocType = "HST STudy 2"
                 
                       {

                             vDocType = "HSTStudy2"
                             vDir = "HSTStudy2\"
                       }


     else
     

                 if vDocType = "HST STudy 3"
                 
                       {

                             vDocType = "HSTStudy3"
                             vDir = "HSTStudy3\"
                       }


     else
     

                 if vDocType = "HST Questionnaire"
                 
                       {

                             vDocType = "HSTDoc"
                             vDir = "HSTDOC\"
                       }

     else
     

                 if vDocType = "Interp 1"
                 
                       {

                             vDocType = "Interp"
                             vDir = "Interp\"
                       }


     else
     

                 if vDocType = "Interp 2"
                 
                       {

                             vDocType = "Interp2"
                             vDir = "Interp2\"
                       }


     else
     

                 if vDocType = "Interp 3"
                 
                       {

                             vDocType = "Interp3"
                             vDir = "Interp3\"
                       }
           

     else
     

                 if vDocType = "Hst Recieved Doc"
                 
                       {

                             vDocType = "HSTRec"
                             vDir = "HSTRec\"
//Writeln(vDocType)
//Writeln(vDir)


                       }
     else
     

                 if vDocType = "HST Sent Back Doc"
                 
                       {

                             vDocType = "HSTSback"
                             vDir = "HSTSback\"



                       }

// This is setting the local directory of where the dialog box is to open to select files
LocalCWD("c:\Attach")
// this runs the pick the file dialog
vresult = @localfiledialog("choose a Document to work with", "*.pdf")
           


     if  Vresult = ""

Then

     {
     @Msgbox("","You Have not selected any Document to process","")
     LocalCWD("C:\sesame\") // puts local path back to C sesame
     
     }
else


     {
// Sets the name to use during renaming, moving and displaying pdf
vrname = (ptid + vDocType +".pdf")
//Writeln(vrname)
vDirNfile = (@ClientLocalValue("pathVariable") + vdir + vrname)
//Writeln(vDirnfile)



// check to see if a file already exists so it will append it instead of replacing it (you will need a file utility called merge)

     
iF      FileExists(vDirNfile) // needs to be changed based on working directory
     {
     
m = @shell("c:\sesame\merge.exe -qm " + vresult + " " + vDirNfile  + " -o " + vDirNfile)

D = @Shell("Move C:\Attach\*.pdf c:\store")





     }
     else
     {
           // Renames pdf from original to new name of patient ID plus word script
           n = @Shell( "ren " + @Chr(34) + vresult + @Chr(34) + " " + @Chr(34) + vrname + @Chr(34) )
           // moves from script directory to done
           m = @Shell( "move " + @Chr(34) + "c:\Attach\" + vrname + @Chr(34) + " " + @Chr(34) + @ClientLocalValue("myscriptpath") + vdir + @Chr(34) )

// this runs my subroutine that makes the checkboxes red or green and a view button visible or not based on if the documents are available
           ynUpdate()

     }



     
// puts local directory back to c:\sesame
LocalCWD("C:\sesame\")


}

}

StreifLicht, how did you put the image in the post of the forum? I want to post a couple of images of my document modules for you to see but I, somehow, cannot upload the image to the forum web-directory. I can use my own site to place the image and display here in the forum post but just wondering, how you did it.

I am not seeing:
________________________________________
Attachement:
Attachment1 --------------------------------- Browse
__________________________________________

Part of the window in my post Reply section. What do I do to bring that up?

As you can see there is no attachment section in spite of expanding the section.

xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Thanks Mark for looking into this.

StreifLicht, I am posting here some images just to give an idea of Document Module. 

StandAlone Document Form



DocumentSubform with mainform




FormAsDialog for inserting new records



DocumentSubMenu on pressing the document button on mainform



On choosing view section - it display all documents in the record - one can choose to open it.

Manage Database ----> DatabaseName ----> Managefields --->Change Field Name --->fill the new Name --->  Add transaction to Batch ---> Run Batch

The above should change the field's name and it will be reflected in the property Viewer.

There are 3 things, namely

Label
Element Name
Field Name

It is Element name is displayed in Program Editor

You can change the Element Name in Property Editor

Select Element by clicking it ---> Property Editor -> Other tab ---> Name --> <F5> will bring on current Name ----> Type over the new Name -->Press the arrow on the right side end to take the effect ----> view the change of Name in property viewer ----> the name change will be also reflected in the Program Editor.

Just to clarify the basic:

Element Label and Name deals with Layout or Forms while fields is to database. One application can have multiple databases and one database can have multiple forms.

As far as I know all commands in layout deals with Element Names except @XResultset ( ) commands, that works directly on database and hence uses field name.

0 - Default position (100 pixels left of the right top edge of the main window).
1 - Absolute screen position of xpos and ypos.
2 - xpos and ypos relative to the top left corner of the main window.
3 - xpos and ypos relative to the top left corner of the form's window.
4 - xpos and ypos relative to the form's top left corner.

I usually use:

PopupSelectPosition(4, @Xpos(LEName), @Ypos(LEName))

This is relative to the button or the element where the code is placed. (You do not have to name the LEName)  Use the code as it is. LEName defaults to the LE the code is in.

This way the popup will be right by the subject element.

LEName is Layout Element Name right?
This works  Thank you again Bharat.
Currently i play around with some snippets
to learn the basics. Im not a programmer
so it will take some time... 

Quote:


Other than Lanticans, most of us here are amateurs. Thanks to Sesame for providing us with the platform and all the tools, so that we can design and program applications just like programmers do and give us ability to see how the logic is put to use through programming. Without unparalleled support by Lanticans, none of these would work! Thanks for all the support.  So, keep going with your own speed. We all have passed through that and we understand.

Carl, you are right! LEName should be replaced by ThisElement, that will take the current element as reference point.