mloucel
Member
- Local time
- Today, 00:05
- Joined
- Aug 5, 2020
- Messages
- 359
Darn@mloucel
Ha! Unwarranted flattery will get younowhereeverywhere!It’s certainly been available for many years yet for some reason doesn’t seem to be widely known about.
I’m not sure about the MID acronym as i immediately reversed it! DIM Isladogs as … (insert your choice of words here)
the db is still not production, and I am planning to use a NAS drive instead of the server, even later IF I LEARN ENOUGH, I will move the BE to SQL SERVER, I found somewhere that there is a piece of software that moves all the tables to SQL with min effort, and apparently works pretty good, so for now I need it here with me, in my cozy PC, once is completely working with at least 99% accuracy and my boss is happy, I will send it to the NAS, for people to play around, meanwhile I will do my best to move it to SQL, we have [or I HAVE] until January, so plenty of time.But WHY? This is a bad idea and unnecessary. If you are afraid you will mess up and test with the production BE, then add some code to it to warn yourself if the FE is running on your computer but is linked to the production BE. I have code that turns the header section of a form a funky color like lime green when I am using a FE linked to the production BE.
I found somewhere that there is a piece of software that moves all the tables to SQL with min effort,
If you do that you are back to the same issue. It's hard to develop new facilities as you are always working on the live database.i recently came into the same situation described in this thread. i have a follow up question to this. is there any way to get both the FE and BE into a single application (unsplit)? so basically i'll only have one .MDB file?
thanks for any suggestions everyone.
I always split mine now, and I am the only user. That way if I muck up the code side of things, my data is safe?There really is no reason not to split a database, unless you are going to be the only user.
Thanks @Pat Hartman and everyone else, I see your point, just a little reminder, most of us that ask to undo the split is because we are newbies, the knowledge you all have is of utmost importance, to me at least, is a moment to learn, a way to understand that undoing the split is unnecessary, but in our eyes and poor understanding of how thinks work, makes it harsh to see your opposition, we do want to believe that we are in the "RIGHT" when we are in the "WRONG".During early development, when the tables are somewhat in flux, it is more convenient to develop with embedded tables regardless of whether they will ultimately end up as SQL Server or ACE once split. This is because the Access environment gives you some help with propagating changes. But, once you are ready to deploy, you must split and once done can never go back. At that point, you shouldn't be changing column and table names and so the built in Name Auto Correct feature isn't available but that shouldn't be a problem because at that stage in the development, you're still changing names, you've got bigger problems.
Anyway, even apps I build for myself are split if there is any permanence to the data. I use a relinking routine so that when the db opens, it makes sure the app is linked to the BE that is in the same folder as the FE. That way if I use the app from a thumb drive, it automatically links even when the drive letter changes because the drive is plugged into a different computer.
I saw the video finally, that is just outstanding, but means, is not easy as I thought it will be, you were able to fix the nulls since you know HowTo and WhereTo, but a layman as me will be lost as cannibal in the middle of Manhattan
The thing is that you CAN come here to ask for information on solving any specific issues that come up.I saw the video finally, that is just outstanding, but means, is not easy as I thought it will be, you were able to fix the nulls since you know HowTo and WhereTo, but a layman as me will be lost as cannibal in the middle of Manhattan, but nevertheless I can always come here and ask.