It should work. I don't see why not. As long as you don't have any conflicting names. Make a backup copy of everything and give it a try. Can't hurt.

we do have a module in the one we are building and also one in the calendar.  So should I copy the module info from the calendar and paste it into the module in the one we are building?

You can have multiple modules, in fact, a good database usually will. Just make sure none of the function or sub names are the same. Like you can't have a Status global function in one module and have the same thing in another one.

I had to redo the query.  It kept saying it was having a compile error.  So I  changed the DateTime field to a concatenation of an apptDate and ApptTime field.  That will let the dog groomer change date and/or time if she wants to but still keep the DateTime field that was used.  I am not familiar with the FORMAT command that was being used. I see that there are 2 functions with the same name IsLoaded.  I renamed the one we did while making the database IsLoaded1 to see if that would allow the calendar to open and it does... now I have to remember where we called it from. lol  the little pop up apptlistf form to enter appointment info or see appointments isnt showing the date and times on the left side so need to figure out why... its a puzzle to figure out

Yeah, it's sometimes a process of elimination, just going through and figuring out what is doubled and what is not. Usually, a compile will tell you if you've got duplicated objects or not, as far as VBA goes.

Okay... so, I see the issue with using the Query.  You stopped using the query and the calendar is based on the CalendarT...  so... trying to figure out how I can take my date field and my time field and merge them into the datetime field you are using.  read you can say [DateTime] =[ApptDate] + [ApptTime] but that just gives me 0's. I will make this happen!  lol

I did it!!!  I took out the datetime before the equals, the system deleted the = and now i have my DateTime field with date and time... wohoo!!  now to see if it fixes my calendar issue

Okay.... I need this explained to me... It is just not making sense.  As I mentioned, The GlobalMod in the Calendar has a function called IsLoaded.  The database we have been building also has a function called IsLoaded.  So...I decided to make my changes to the calendar program field names and such so nothing will clash when I move it over.  So... I added a 2 after IsLoaded so it would be a different name from the IsLoaded in my database.  I used the FIND thing to find all of the IsLoaded's and added a 2 after each one.  No reason I can think of that it would not work.  so I save everything and then click DatePickerF to open it and I get a runtime error 438: Object doesn't support this property or method.  When I click Debug it takes me to the Public Function IsLoaded2.  If I go back and delete the number 2 then everthing works fine.  I thought maybe it cant be a number for some weird reason so added an extra d and same thing... take the d off and works.  What is going on??

That line is looking for the IsLoaded property of the form specified by FormName. You can't change that.

So if you want to rename the function, you'll need to say:

Public Function IsLoaded2 (FormName As String) As Boolean
    IsLoaded2 = CurrentProject.AllForms(FormName).IsLoaded
End Function

Yes, it's confusing. I know, but this is what happens when you try to merge two databases where you have duplicate function names. It can be a mess.

Thank you,  that does seem to be working.  I can see where I went wrong...  IsLoaded is one of the choices when you are writing the string and is not the Function Name.  Totally makes sense.  Yeah... I can see now how things can get really messy trying to merge.  Glad I tried it with a small database with not a ton of code.  Thank you so much Rick! I definitely learned some things.  I do have your voice in my head saying if you want to know if  something will work...  try it... see what happens...

Yes, definitely. That is the best way to learn. Just make sure you back everything up first.