Combo's [Edit from Record] help

[MajP]

I have done the same and sometimes hard to see the forest for the trees.

 

[mloucel]

I have done the same and sometimes hard to see the forest for the trees.

A million thanks @MajP for your guidance and support, the "moster" is alive, because it doesn't even make it to monster, is working with all the defects and gross programming, but is alive and well.

If you have any other suggestions I am welcoming them with open eyes and ears.

Thanks as well to @Pat Hartman with a million sincere apologies for any misunderstanding, I was at the eleventh hour and 4 months of goods and bads, this has been a total adventure where I learn a lot and many times you save me as well.

Now that the program is in "Production" mode I still have more to do, reports, and changes that will come with the time, I need to polish it a bit more, and this time I will ask for help when I am struggling, I have learned a valuable lesson, "sometimes hard to see the forest for the trees."

Maurice.

 

[MajP]

If you have any other suggestions I am welcoming them with open eyes and ears.

From a cursory glance this seems well designed. I can find my way around and figure out what is going on
1. Table and field names are clear and proper
2. Table design and data relationships looks well designed
3. Code is clear, variables understandable
4. Code is well organized and concise
5. Looks well designed so you can continue to add features

To make things easier for you, you may want to add to the forms so you can test them without having to go through the flow. In other words open from the navigation pane.
For example if the form uses open args and openargs are not passed I check for this case and do not throw an error. Might put a message "No Args passed.". This way it runs through remaining code and as an admin I can check the form without having to open some other forms to get to it..
Also check if Tempvars("SCM") exists before setting menu

Once I split a database I always have relink code.
The user opens the db and it checks that all tables are linked. If not prompts the user to use a file browser to locate the backend. This is very useful in development for working between a production BE and a development BE and being able to move them around. If not when you give the user an FE you may have to manually link locations. If you need that I can provide. If not how are you distributing and linking to the proper BE? Normally the path from your computer may not be the same as the User. Even if on the network.
Also how do you plan to distribute updates. You can search on here for a lot of updater code. Often the actual Front end is on the network and the user has a link to a batch file. Then it checks version to the version on the backend and if not the most current the new version is downloaded.

 

[MajP]

Another thing you may want to add is logging errors.
You do not have a lot of error handling. If you add it you probably want to send it to some kind of log so you can see where the problems are. Popping up a message does nothing. Logging it allows you to know what to fix. You can find plenty of code for that.
You might need an audit trail if you have lots of uses doing updates. You can find plenty of code on that.
For reporting you probably want to give the user the ability to select a report and choose to export to PDF, RTF, Show as access report, Print. I have some code on that I use.
Reporting is an Art. You want to create and maintain few reports but have the ability to filter and sort and thus creating many many ways to show the same report.

 

[mloucel]

From a cursory glance this seems well designed. I can find my way around and figure out what is going on
1. Table and field names are clear and proper
2. Table design and data relationships looks well designed
3. Code is clear, variables understandable
4. Code is well organized and concise
5. Looks well designed so you can continue to add features

To make things easier for you, you may want to add to the forms so you can test them without having to go through the flow. In other words open from the navigation pane.
For example if the form uses open args and openargs are not passed I check for this case and do not throw an error. Might put a message "No Args passed.". This way it runs through remaining code and as an admin I can check the form without having to open some other forms to get to it..
Also check if Tempvars("SCM") exists before setting menu

Once I split a database I always have relink code.
The user opens the db and it checks that all tables are linked. If not prompts the user to use a file browser to locate the backend. This is very useful in development for working between a production BE and a development BE and being able to move them around. If not when you give the user an FE you may have to manually link locations. If you need that I can provide. If not how are you distributing and linking to the proper BE? Normally the path from your computer may not be the same as the User. Even if on the network.
Also how do you plan to distribute updates. You can search on here for a lot of updater code. Often the actual Front end is on the network and the user has a link to a batch file. Then it checks version to the version on the backend and if not the most current the new version is downloaded.

Well thanks Sir,

SCM is created before the Main Menu so it will always be there, I did that on purpose.
I have set the BE in a NAS drive, I created a Batch file that created Drive H for ALL users [Never Used], then the BE DB is linked specifically to Drive H.
The FE is created as well in Drive C using the same batch file, if the batch file detects is a new install, creates ALL of the paths and drives, if not then only updates the FE, of course previously I make sure all users have access to that folder on the NAS, I chose a NAS because has less issues than a server and I am trying to remove all servers from the network.
I will check for Updaters, and I will try to update this accordingly.

I will recheck all your, advise and go accordingly as well.