Jump to content
Claris Platform 2023 Roadmap ×

Access code to FileMaker

This topic is 6146 days old. Please don't post here. Open a new topic instead.

Recommended Posts

This is the code I use to create a database of dates. Can someone tell me how to do this in Filemaker?


Function filldates2(sdate As Double, edate As Double)

Dim i As Double

Dim j As Double

Dim db As Database

Dim rs As Recordset

Set db = CurrentDb()

Set rs = db.OpenRecordset("TblDates", DB_OPEN_DYNASET)

Dim numdates As Double

numdates = edate - sdate

For i = 1 To numdates

For j = 1 To 2


rs!Date = sdate + i

rs!SessionLength = IIf(j = 1, "AM ONLY", "PM ONLY")


Next j

Next i


End Function

Link to comment
Share on other sites

The code, which I guess is simpler in FileMaker than in Access, should allow me to generate a table just containing dates. I want to be able to enter 2 dates (1st Jan to 31 August for example) and then generate a table containing all the dates from and to those dates. Once joined to a booking table and viewed as a table, this will show me what dates are still free and what dates are booked, which is better visually when you are trying to find a free date while on the phone to someone.

Link to comment
Share on other sites

Your original code includes some obfuscations--what's with the AM/PM? Setting that aside, I will simply address the direct question, which is how to turn your code into a FileMaker script.

First, you will need a way to handle sdate, edate, and a counter. Method A (usable in most versions of FM) uses global fields to store these values. Method B (useable in FM7 and later) is to use a Script Parameter. Method C (valid in FM8) is to use variables. Because I am most familiar with Method A, I'll use it (note it's also the most unsavory WRT database design/programming precepts). You can look into the other ways at your discretion.

To create the global fields, go into Define Database and add an sdate and edate fields to the table in question. Each will be a date field that uses global storage. Global field gCounter will be a number field using global storage.

With the fields created, create a means of populating them. You can either have a custom dialog box with both global fields on it, or a specific layout with them on it.

Having established the fields, your script could look like:


Go To Layout["TheLayoutForTheRightTable"]

Set Field["gCounter"; 0]


Exit Loop If [sdate + gCounter = edate]

New Record/Request

Set Field[realDate; sdate + gCounter]

Set Field[gCounter; gCounter + 1]

Commit Record

End Loop

No doubt others will offer different approaches, but I hope this sets you on your way.


Link to comment
Share on other sites


AFAIK, the Set Field command is the same in 8.5 as it is in 7 (but obviously, since I'm on 7 I can't say for sure). Perhaps you have not checked the "Specify" option for the Set Field script step?

WRT "realdate", that was my way to say "set the field in your database table that is supposed to hold your 'real' date for each entry of the result set." So, if your db table uses a field called "ApptDate", set THAT field.

Your original code set a db column named "date." You REALLY don't want to use "date" as the name of a field in your table (in ANY database system). I guarantee that you'll at the least be confused in development when you try to remember that "date" is the name of your field AND the name of a command and datatype. Moreover, you'll have severe troubles if you want to use ODBC.

That was why I used the made-up name of "realdate."



Link to comment
Share on other sites

This topic is 6146 days old. Please don't post here. Open a new topic instead.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.